← previous blocknext block →recent activity

Analyzing

Block #94,753,644

14 transactions · 13 stateful · 2026-08-10 10:39:43 UTC

Parallelism

86/100

Blocked

23%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #94,753,644  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5e5bcbbc…a932

0x968279…9342

4 touches
1 conflict

0x5e5bcbbc…a92f

0x968279…9342

4 touches
1 conflict

0x5e5bcbbc…a930

0x968279…9342

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x5d6e4470…4b4c

0x34b655…2a6f

4 touches
1 conflict

0x66bdb4c2…7ea6

0x34b655…2a6f

4 touches
1 conflict

0x70a1ac1f…e2d1

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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: 0x96827978…f09342

1 conflict on slot 0x5e5bcbbc29…bea932

← previous block·next block →recent activity