← previous blocknext block →recent activity
Analyzing
Block #84,081,462
19 transactions · 17 stateful · 2026-06-27 17:56:45 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,081,462 · 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
1w02w13w04w15w26w07w010w111w013w014w116w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4e19ae4…0788
0xe7cd86…c82d
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x454d8940…cfe7
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x89d753fb…f258
0x34b655…2a6f
4 touches
1 conflict
0x8d0e98f3…7ba0
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: 0xe7cd86e1…0fc82d
3 conflicts on slot 0xc4e19ae47e…dc0788
Audit this contract →
← previous block·next block →recent activity