← previous blocknext block →recent activity
Analyzing
Block #72,970,920
23 transactions · 20 stateful · 2026-05-07 06:30:57 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,970,920 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w06w17w28w113w014w015w116w217w118w019w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a354a63…0515
0x065c9d…c394
8 touches
6 conflicts
0x251861eb…78fd
0x34b655…2a6f
8 touches
6 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
6 touches
3 conflicts
0x0520da1d…c88e
0x34b655…2a6f
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
6 touches
3 conflicts
0x0eac6378…36f4
0x34b655…2a6f
6 touches
3 conflicts
0x150af51d…9c42
0x34b655…2a6f
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x2a354a6333…480515
Audit this contract →
← previous block·next block →recent activity