← previous blocknext block →recent activity
Analyzing
Block #86,691,463
16 transactions · 14 stateful · 2026-07-09 20:05:48 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,691,463 · 16 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
1w02w17w08w111w112w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ba014e3…35d5
0x34b655…2a6f
6 touches
3 conflicts
0xffd93b8b…e1e7
0x34b655…2a6f
4 touches
1 conflict
0x968d162d…d001
0x34b655…2a6f
4 touches
1 conflict
0xa243ce39…3ff4
0x34b655…2a6f
4 touches
1 conflict
0xb9eeefc7…cf3c
0x34b655…2a6f
4 touches
1 conflict
0xc501c026…8bc3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdcf93b63…ae96
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 0x3ba014e38a…cf35d5
Audit this contract →
← previous block·next block →recent activity