← previous blocknext block →recent activity
Analyzing
Block #86,922,961
14 transactions · 12 stateful · 2026-07-10 21:52:52 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,922,961 · 14 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
5w08w19w210w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0237ed3…2622
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbb30c41f…1385
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe1386ead…43ad
0x34b655…2a6f
4 touches
1 conflict
0x58627b98…92ad
0x34b655…2a6f
4 touches
1 conflict
0x58627b98…92ae
0x34b655…2a6f
4 touches
1 conflict
0x606bc50d…4c10
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 0xa0237ed311…832622
Audit this contract →
← previous block·next block →recent activity