← previous blocknext block →recent activity

Analyzing

Block #84,358,606

19 transactions · 16 stateful · 2026-06-29 00:43:02 UTC

Parallelism

84/100

Blocked

31%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,358,606  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…0002

0xd637b3…4160

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0x2d2168c4…af1b

0x34b655…2a6f

4 touches
1 conflict

0x3287e4ec…eaa3

0xa6afd3…d132

4 touches
1 conflict

0x975680c7…0e39

0xa6afd3…d132

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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: 0xd637b38f…c64160

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity