← previous blocknext block →recent activity
Analyzing
Block #86,660,628
20 transactions · 13 stateful · 2026-07-09 16:40:02 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,660,628 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w19w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32f1fe90…5ee3
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0xdb585e4b…55f4
0x40c49f…2af0
4 touches
1 conflict
0xdf15e2bf…d7a9
0x34b655…2a6f
4 touches
1 conflict
0xed4bf91e…3788
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x5097063c…716f
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e2
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
6 conflicts on slot 0x32f1fe903a…fd5ee3
Audit this contract →
← previous block·next block →recent activity