← previous blocknext block →recent activity
Analyzing
Block #87,330,766
26 transactions · 24 stateful · 2026-07-12 19:19:09 UTC
Parallelism
85/100
Blocked
46%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,330,766 · 26 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
1w03w04w15w26w07w18w09w110w211w012w013w117w118w219w320w324w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb6ed530c…d450
0x34b655…2a6f
8 touches
6 conflicts
0x52e69143…95ad
0x065c9d…c394
8 touches
6 conflicts
0xca496ab2…26ce
0x34b655…2a6f
6 touches
3 conflicts
0x02edde27…c16a
0x065c9d…c394
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x16730d5b…f1e7
0x34b655…2a6f
6 touches
3 conflicts
0x288961aa…ac7f
0x34b655…2a6f
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