← previous blocknext block →recent activity
Analyzing
Block #86,232,160
22 transactions · 16 stateful · 2026-07-07 16:54:25 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,232,160 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w012w013w114w116w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x9cf2efe9…de36
0xd32edf…ff58
3 touches
1 conflict
0x0d3b978b…5e8e
0x34b655…2a6f
2 touches
0 conflicts
0x54fc1ac2…a311
0x34b655…2a6f
2 touches
0 conflicts
0x8eef368f…aa21
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 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity