← previous blocknext block →recent activity

Analyzing

Block #84,361,601

20 transactions · 19 stateful · 2026-06-29 01:03:01 UTC

Parallelism

80/100

Blocked

42%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,361,601  ·  20 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

0x00000000…0002

0xd637b3…4160

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb1f0701d…4f4a

0xc8689a…ee79

4 touches
1 conflict

0x2f4d415d…5f95

0x34b655…2a6f

4 touches
1 conflict

0x7500c6c7…6b90

0x34b655…2a6f

4 touches
1 conflict

0x7c6984da…21e5

0x34b655…2a6f

4 touches
1 conflict

0xc61ba77e…ff5a

0x065c9d…c394

3 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