← previous blocknext block →recent activity
Analyzing
Block #74,023,140
10 transactions · 8 stateful · 2026-05-12 03:31:49 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,023,140 · 10 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
1w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x2d430d12…0d25
0x065c9d…c394
2 touches
0 conflicts
0xa82c5d38…d9a1
0x065c9d…c394
2 touches
0 conflicts
0xaeae6f96…a4fe
0x065c9d…c394
2 touches
0 conflicts
0xc1635ba7…7920
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 0xbd7e37a9b5…859eb5
Audit this contract →
← previous block·next block →recent activity