← previous blocknext block →recent activity
Analyzing
Block #74,023,014
32 transactions · 19 stateful · 2026-05-12 03:30:59 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,023,014 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w112w213w314w017w018w121w122w423w525w229w330w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x0b390c61…dc07
0x065c9d…c394
10 touches
10 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
10 touches
10 conflicts
0xecea1644…e1cb
0xd32edf…ff58
9 touches
10 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
8 touches
6 conflicts
0x6b319071…a105
0xc8689a…ee79
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x3e4b8d9f…b8a7
0x5d823e…89c6
6 touches
5 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