← previous blocknext block →recent activity
Analyzing
Block #74,630,204
19 transactions · 18 stateful · 2026-05-14 22:58:45 UTC
Parallelism
74/100
Blocked
67%
Avg conflicts / tx
1.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,630,204 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w37w08w19w210w311w012w113w414w417w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
10 touches
10 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0xfe3d37ee…6e67
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0373ff8f…7b95
0x065c9d…c394
5 touches
3 conflicts
0x904fc3c0…00ec
0x34b655…2a6f
4 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 0xffe431af56…838faa
Audit this contract →
← previous block·next block →recent activity