← previous blocknext block →recent activity
Analyzing
Block #86,532,531
23 transactions · 23 stateful · 2026-07-09 02:20:52 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,532,531 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w07w110w211w112w017w118w219w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x1bd46462…e65c
0x34b655…2a6f
4 touches
1 conflict
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0x2b070180…7ca7
0x34b655…2a6f
4 touches
1 conflict
0x42e08579…09bb
0x34b655…2a6f
4 touches
1 conflict
0x45e5059c…bcb1
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity