← previous blocknext block →recent activity
Analyzing
Block #74,668,880
8 transactions · 7 stateful · 2026-05-15 03:16:45 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,668,880 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa1b570e0…bb88
0x065c9d…c394
3 touches
1 conflict
0xd3877320…128f
0x065c9d…c394
3 touches
1 conflict
0x2534530d…c2f3
0x065c9d…c394
3 touches
1 conflict
0x9ba32414…c8c0
0x065c9d…c394
3 touches
1 conflict
0x337fcbd5…83e1
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity