← previous blocknext block →recent activity
Analyzing
Block #84,996,411
22 transactions · 19 stateful · 2026-07-01 23:34:24 UTC
Parallelism
77/100
Blocked
32%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,996,411 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w19w010w117w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2b740aa…b524
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xec71d7fa…def3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x478e6e08…83bf
0x34b655…2a6f
4 touches
1 conflict
0x85b992ec…db0e
0x34b655…2a6f
4 touches
1 conflict
0xcc2cd268…5687
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: Perpl
6 conflicts on slot 0xe2b740aa0d…82b524
Audit this contract →
← previous block·next block →recent activity