← previous blocknext block →recent activity
Analyzing
Block #86,656,364
11 transactions · 7 stateful · 2026-07-09 16:11:33 UTC
Parallelism
82/100
Blocked
14%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,656,364 · 11 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x38b61269…48d7
0x34b655…2a6f
4 touches
1 conflict
0x00eda7de…66f6
0x34b655…2a6f
2 touches
0 conflicts
0x02da711a…726e
0x34b655…2a6f
2 touches
0 conflicts
0x02da711a…726f
0x34b655…2a6f
2 touches
0 conflicts
0x13ca795c…db00
0x34b655…2a6f
2 touches
0 conflicts
0x19b56cc2…5c6b
0x34b655…2a6f
2 touches
0 conflicts
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 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity