← previous blocknext block →recent activity
Analyzing
Block #74,499,676
11 transactions · 9 stateful · 2026-05-14 08:21:59 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,499,676 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0xca04c7ad…7612
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x6f8feb41…121a
0x065c9d…c394
2 touches
0 conflicts
0x99309dfd…6b21
0x065c9d…c394
2 touches
0 conflicts
0xa7f7fe85…b0f3
0x065c9d…c394
2 touches
0 conflicts
0xba68d3ba…343d
0x065c9d…c394
2 touches
0 conflicts
0xc3899f47…ae8f
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
1 conflict on slot 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity