← previous blocknext block →recent activity
Analyzing
Block #86,852,189
26 transactions · 13 stateful · 2026-07-10 13:59:39 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,852,189 · 26 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
5w06w17w19w224w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7fe04a…3c56
0x34b655…2a6f
6 touches
3 conflicts
0xd94ac4d1…edb0
0x34b655…2a6f
4 touches
1 conflict
0xd94ac4d1…edb1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x198bae6a…f31c
0x34b655…2a6f
4 touches
1 conflict
0x3d2404a0…a61b
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x99479bc5…3a88
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 0xec7fe04ad1…2d3c56
Audit this contract →
← previous block·next block →recent activity