← previous blocknext block →recent activity
Analyzing
Block #86,272,457
20 transactions · 18 stateful · 2026-07-07 21:23:30 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,272,457 · 20 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
1w013w114w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0014
0x2f55a2…8375
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03318be6…35cd
0x065c9d…c394
2 touches
0 conflicts
0x0ec46fc4…cbda
0x065c9d…c394
2 touches
0 conflicts
0x10c9c002…c1fa
0x065c9d…c394
2 touches
0 conflicts
0x225c50a9…8f57
0x065c9d…c394
2 touches
0 conflicts
0x26416eb5…22f2
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity