← previous blocknext block →recent activity
Analyzing
Block #72,285,377
13 transactions · 10 stateful · 2026-05-04 02:22:58 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,285,377 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x6dc8104e…ed48
0x065c9d…c394
4 touches
1 conflict
0x2c6c48a9…ba4a
0x065c9d…c394
2 touches
0 conflicts
0x4a324d60…e27a
0x065c9d…c394
2 touches
0 conflicts
0x639f478c…ed77
0x065c9d…c394
2 touches
0 conflicts
0xd771154b…12d6
0x065c9d…c394
2 touches
0 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
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