← previous blocknext block →recent activity
Analyzing
Block #86,682,376
22 transactions · 19 stateful · 2026-07-09 19:05:12 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,682,376 · 22 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
5w06w19w010w111w215w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x256abea8…f282
0x34b655…2a6f
4 touches
1 conflict
0x273c2a35…7513
0x34b655…2a6f
4 touches
1 conflict
0x2f6698be…af57
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x511ecf07…8ed0
0x34b655…2a6f
4 touches
1 conflict
0x5127ece2…b66d
0x34b655…2a6f
4 touches
1 conflict
0x609dd62f…3cb2
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
1 conflict on slot 0x157dbfb216…8d4089
Audit this contract →
← previous block·next block →recent activity