← previous blocknext block →recent activity
Analyzing
Block #74,504,804
18 transactions · 14 stateful · 2026-05-14 08:56:27 UTC
Parallelism
83/100
Blocked
21%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,504,804 · 18 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
1w02w111w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x003d7fb1…bfe5
0x065c9d…c394
2 touches
0 conflicts
0x0373ff8f…7b95
0x065c9d…c394
2 touches
0 conflicts
0x42a58754…1d25
0x065c9d…c394
2 touches
0 conflicts
0x5e9f8ea3…d593
0x065c9d…c394
2 touches
0 conflicts
0xb0ad2353…3356
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity