← previous blocknext block →recent activity
Analyzing
Block #86,696,449
20 transactions · 18 stateful · 2026-07-09 20:39:03 UTC
Parallelism
90/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,696,449 · 20 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
5w07w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85c84f98…06d7
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x70375ad9…bee6
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0934ec4c…50c8
0x34b655…2a6f
2 touches
0 conflicts
0x120933a6…dbe3
0x34b655…2a6f
2 touches
0 conflicts
0x25e3730b…24a9
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 0x85c84f9817…2806d7
Audit this contract →
← previous block·next block →recent activity