← previous blocknext block →recent activity
Analyzing
Block #74,571,809
11 transactions · 11 stateful · 2026-05-14 16:28:17 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,571,809 · 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
1w04w05w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0x1554f0e9…cf8c
0x065c9d…c394
2 touches
0 conflicts
0x1ace91b6…a5f7
0x065c9d…c394
2 touches
0 conflicts
0x35e8d11e…24f6
0x065c9d…c394
2 touches
0 conflicts
0x5ce324b7…0a1e
0x065c9d…c394
2 touches
0 conflicts
0x8f87f247…2281
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