← previous blocknext block →recent activity
Analyzing
Block #74,613,756
11 transactions · 8 stateful · 2026-05-14 21:09:00 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,613,756 · 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
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x2b4a1561…3a58
0x065c9d…c394
2 touches
0 conflicts
0x54582eff…26d1
0x065c9d…c394
2 touches
0 conflicts
0x6362a2d1…a16b
0x065c9d…c394
2 touches
0 conflicts
0x75218c7e…26bd
0x065c9d…c394
2 touches
0 conflicts
0x81086d93…6a19
0x065c9d…c394
2 touches
0 conflicts
0xf219e53d…1a9a
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