← previous blocknext block →recent activity
Analyzing
Block #86,959,598
13 transactions · 12 stateful · 2026-07-11 01:57:39 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,959,598 · 13 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
1w03w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0xcd90c2ef…33c4
0x065c9d…c394
4 touches
1 conflict
0x3525f0f6…9a5d
0x065c9d…c394
3 touches
1 conflict
0x0fbd3a3c…b08c
0x065c9d…c394
3 touches
1 conflict
0x7ed891ec…6b9c
0x065c9d…c394
2 touches
0 conflicts
0x92538302…3eb5
0x065c9d…c394
2 touches
0 conflicts
0xce78e705…dd4a
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity