← previous blocknext block →recent activity
Analyzing
Block #86,688,060
22 transactions · 16 stateful · 2026-07-09 19:43:07 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,688,060 · 22 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
1w010w012w113w114w115w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbca4de0c…577c
0x34b655…2a6f
4 touches
1 conflict
0xf722980d…ce99
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x23f1bee2…d0f4
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x02d79f72…b18e
0x34b655…2a6f
4 touches
1 conflict
0x0380d355…f6b5
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 0xbca4de0cd0…27577c
Audit this contract →
← previous block·next block →recent activity