← previous blocknext block →recent activity
Analyzing
Block #74,629,172
9 transactions · 9 stateful · 2026-05-14 22:51:53 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,629,172 · 9 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xced07c71…46ad
0x065c9d…c394
4 touches
1 conflict
0x87a8c526…80a1
0x065c9d…c394
3 touches
1 conflict
0x81622b08…8402
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x8abd06c9…2da5
0x065c9d…c394
2 touches
0 conflicts
0xe6b6587a…a007
0x065c9d…c394
2 touches
0 conflicts
0xf5ec948b…69c6
0x065c9d…c394
2 touches
0 conflicts
0xb1632c2f…d991
0x0a3323…0a3c
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 0xced07c717a…fd46ad
Audit this contract →
← previous block·next block →recent activity