← previous blocknext block →recent activity
Analyzing
Block #74,948,564
11 transactions · 10 stateful · 2026-05-16 10:23:46 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,948,564 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x266367f8…8bbd
0x065c9d…c394
2 touches
0 conflicts
0x4aa98869…a460
0x065c9d…c394
2 touches
0 conflicts
0x5a1553e2…e9ea
0x065c9d…c394
2 touches
0 conflicts
0xcb898fa2…da97
0x065c9d…c394
2 touches
0 conflicts
0xdc0503bb…b0ed
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity