← previous blocknext block →recent activity
Analyzing
Block #84,332,710
20 transactions · 19 stateful · 2026-06-28 21:50:22 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,332,710 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w18w010w113w014w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xcfe15fba…4f97
0x34b655…2a6f
6 touches
3 conflicts
0x5f3fc680…f989
0x34b655…2a6f
4 touches
1 conflict
0x678e8651…42e7
0x34b655…2a6f
4 touches
1 conflict
0x67dfc52c…cb5f
0x34b655…2a6f
4 touches
1 conflict
0x7425a853…a582
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity