← previous blocknext block →recent activity
Analyzing
Block #86,632,217
25 transactions · 20 stateful · 2026-07-09 13:28:57 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,632,217 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w111w112w015w217w219w323w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eb0ac6b…a73a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x9da6e429…074d
0xa6afd3…d132
6 touches
3 conflicts
0xb43dc900…22f2
0xa6afd3…d132
6 touches
3 conflicts
0x61c12e81…b215
0x34b655…2a6f
6 touches
3 conflicts
0xa9e86552…4f4e
0x34b655…2a6f
4 touches
1 conflict
0xb6225cbd…94e1
0x34b655…2a6f
4 touches
1 conflict
0xfa667abe…bdfc
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 0x8eb0ac6bf2…4da73a
Audit this contract →
← previous block·next block →recent activity