← previous blocknext block →recent activity
Analyzing
Block #86,447,680
22 transactions · 20 stateful · 2026-07-08 16:53:55 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,447,680 · 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
1w02w15w011w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf1a3f1c0…6bb2
0xd32edf…ff58
3 touches
1 conflict
0x21a43f33…991e
0x065c9d…c394
3 touches
1 conflict
0x63a34b68…3eae
0x065c9d…c394
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity