← previous blocknext block →recent activity
Analyzing
Block #84,332,274
12 transactions · 11 stateful · 2026-06-28 21:47:27 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,332,274 · 12 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
2w03w18w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbb3504d4…b05f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0xda5e0705…ecb9
0x34b655…2a6f
4 touches
1 conflict
0xe99ebc4d…22f9
0x34b655…2a6f
4 touches
1 conflict
0x3f7ad3a0…de3b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity