← previous blocknext block →recent activity
Analyzing
Block #86,969,051
12 transactions · 11 stateful · 2026-07-11 03:00:53 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,969,051 · 12 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
1w05w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x63a34b68…3eae
0x065c9d…c394
2 touches
0 conflicts
0x8d1c2dd4…9bf1
0x065c9d…c394
2 touches
0 conflicts
0x8f77c4f2…61b6
0x065c9d…c394
2 touches
0 conflicts
0x9035f7f8…2540
0x065c9d…c394
2 touches
0 conflicts
0xd284732e…8692
0x065c9d…c394
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity