← previous blocknext block →recent activity
Analyzing
Block #74,247,733
10 transactions · 9 stateful · 2026-05-13 04:25:45 UTC
Parallelism
40/100
Blocked
56%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,247,733 · 10 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x109426fa…54e2
0x065c9d…c394
3 touches
1 conflict
0xc1ed2457…b73d
0x065c9d…c394
3 touches
1 conflict
0x7ecaa647…e5c1
0x065c9d…c394
3 touches
1 conflict
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity