← previous blocknext block →recent activity
Analyzing
Block #74,224,577
9 transactions · 8 stateful · 2026-05-13 01:51:50 UTC
Parallelism
33/100
Blocked
63%
Avg conflicts / tx
1.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,224,577 · 9 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
1w02w13w24w35w46w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa5314804…0e4c
0x065c9d…c394
3 touches
1 conflict
0xaf6babfc…d344
0x065c9d…c394
3 touches
1 conflict
0xd66688c3…abc7
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity