← previous blocknext block →recent activity
Analyzing
Block #74,231,764
20 transactions · 18 stateful · 2026-05-13 02:39:34 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
2.1
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,231,764 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w010w211w312w313w414w515w616w717w818w919w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0xf823e97f…2ee6
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
8 touches
6 conflicts
0xc21dceb4…d343
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x4ecdc689…c4e4
0xd32edf…ff58
3 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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity