← previous blocknext block →recent activity
Analyzing
Block #74,451,768
16 transactions · 11 stateful · 2026-05-14 03:03:15 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,451,768 · 16 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
1w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x85a3a365…bbb9
0x065c9d…c394
3 touches
1 conflict
0xa0d06272…7893
0x065c9d…c394
3 touches
1 conflict
0xb88da7cd…07af
0x065c9d…c394
2 touches
0 conflicts
0xf5061a6a…ccf6
0x065c9d…c394
2 touches
0 conflicts
0x1dab10a0…6f3b
0x1001ff…1001
2 touches
0 conflicts
0xc6f1b3af…c97c
0x1001ff…1001
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity