← previous blocknext block →recent activity
Analyzing
Block #92,008,587
23 transactions · 22 stateful · 2026-07-31 20:14:06 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,008,587 · 23 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
2w03w14w08w19w010w111w214w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0xd922e7fc…f57b
0x7b9256…1fb2
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0xd922e7fc…f57c
0x7b9256…1fb2
6 touches
3 conflicts
0x1a6ac8c2…2004
0x7b9256…1fb2
6 touches
3 conflicts
0x1a6ac8c2…2001
0x7b9256…1fb2
6 touches
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity