← previous blocknext block →recent activity
Analyzing
Block #86,766,458
19 transactions · 17 stateful · 2026-07-10 04:26:45 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,766,458 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w09w010w114w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x008d197a…7a6d
0x34b655…2a6f
4 touches
1 conflict
0x0c69433a…4f81
0x34b655…2a6f
4 touches
1 conflict
0x1586ff62…0ebe
0x34b655…2a6f
4 touches
1 conflict
0x1928db9c…6ea9
0x34b655…2a6f
4 touches
1 conflict
0x1a28e34b…1404
0x34b655…2a6f
4 touches
1 conflict
0x1f77dbef…4d32
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
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 0x008d197a8d…657a6d
Audit this contract →
← previous block·next block →recent activity