← previous blocknext block →recent activity
Analyzing
Block #74,428,881
9 transactions · 8 stateful · 2026-05-14 00:30:51 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,428,881 · 9 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbbee74c2…567a
0x065c9d…c394
6 touches
3 conflicts
0x92afbd00…681e
0x065c9d…c394
3 touches
1 conflict
0x671dbe67…c752
0x065c9d…c394
3 touches
1 conflict
0x2b68704d…0944
0x065c9d…c394
2 touches
0 conflicts
0x335fae8e…012c
0x065c9d…c394
2 touches
0 conflicts
0x7feca1f4…1b98
0x065c9d…c394
2 touches
0 conflicts
0x0872abbe…9c39
0x2a68ba…90c5
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