← previous blocknext block →recent activity
Analyzing
Block #74,924,219
14 transactions · 11 stateful · 2026-05-16 07:41:01 UTC
Parallelism
57/100
Blocked
45%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,924,219 · 14 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
1w02w13w26w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0xb41e65df…4994
0xd32edf…ff58
5 touches
3 conflicts
0xba5743c7…21c4
0x1b6862…e19c
4 touches
1 conflict
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x9c62b68f…9fd6
0x065c9d…c394
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity