← previous blocknext block →recent activity
Analyzing
Block #86,909,952
19 transactions · 15 stateful · 2026-07-10 20:26:00 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,909,952 · 19 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
3w07w19w110w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0b277fb8…2d82
0x34b655…2a6f
4 touches
1 conflict
0x140191c8…1ced
0x34b655…2a6f
4 touches
1 conflict
0x230ace69…ed93
0x34b655…2a6f
4 touches
1 conflict
0x230ace69…ed94
0x34b655…2a6f
4 touches
1 conflict
0x2f1b724a…accf
0x34b655…2a6f
4 touches
1 conflict
0x2f4e174d…2803
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 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity