← previous blocknext block →recent activity

Analyzing

Block #94,481,083

17 transactions · 13 stateful · 2026-08-09 11:47:27 UTC

Parallelism

76/100

Blocked

54%

Avg conflicts / tx

0.76

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,481,083  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0xf12242dd…ef35

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x5502e1cc…3910

0x34b655…2a6f

4 touches
1 conflict

0x7e0b7922…c351

0x754704…b603

4 touches
1 conflict

0xa2478c84…6956

0x754704…b603

4 touches
1 conflict

0x05b1b07a…7a99

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Kuru Exchange: MarginAccount

6 conflicts on slot 0x002fed350f…7379fa

← previous block·next block →recent activity