← previous blocknext block →recent activity
Analyzing
Block #74,225,001
8 transactions · 8 stateful · 2026-05-13 01:54:38 UTC
Parallelism
38/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,225,001 · 8 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
1w03w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xba5b4d40…983d
0x065c9d…c394
4 touches
1 conflict
0xb357ec5b…af0e
0x065c9d…c394
3 touches
1 conflict
0x8306ffcf…965a
0x065c9d…c394
2 touches
0 conflicts
0x852afbda…4b79
0x065c9d…c394
2 touches
0 conflicts
0xe5ec4f52…15e2
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity