← previous blocknext block →recent activity
Analyzing
Block #87,620,639
22 transactions · 19 stateful · 2026-07-14 03:38:28 UTC
Parallelism
82/100
Blocked
53%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,620,639 · 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
1w02w03w15w06w17w210w111w012w113w014w215w116w217w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x8f825eeb…9942
0x851145…3f07
6 touches
3 conflicts
0x1d84bebc…07d0
0x34b655…2a6f
4 touches
1 conflict
0x1d84bebc…07d1
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x3cef6445…87da
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity