← previous blocknext block →recent activity
Analyzing
Block #86,668,400
17 transactions · 12 stateful · 2026-07-09 17:31:52 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,668,400 · 17 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
1w02w13w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59f58019…2973
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2878
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1aa
0xb1dbf0…c0d3
4 touches
1 conflict
0xe8a876d4…921a
0xb1dbf0…c0d3
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x5f72d58f…c445
0x34b655…2a6f
2 touches
0 conflicts
0x70e3da66…674a
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 0x59f58019fc…bc2973
Audit this contract →
← previous block·next block →recent activity