← previous blocknext block →recent activity
Analyzing
Block #72,311,189
25 transactions · 19 stateful · 2026-05-04 05:15:30 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,311,189 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w09w110w215w116w217w318w421w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf3283ba…c9fa
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x7b7bcac3…8fbf
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x005fb969…2d97
0x34b655…2a6f
4 touches
1 conflict
0x17e2d2a0…359e
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
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 0xcf3283bab2…c3c9fa
Audit this contract →
← previous block·next block →recent activity