← previous blocknext block →recent activity
Analyzing
Block #72,172,948
10 transactions · 9 stateful · 2026-05-03 13:47:25 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,172,948 · 10 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
2w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x0eb7e6ff…cd34
0x065c9d…c394
4 touches
1 conflict
0xfb747647…ea39
0x065c9d…c394
4 touches
1 conflict
0xe82db774…09a1
0x065c9d…c394
3 touches
1 conflict
0xf38a7b55…ab85
0x065c9d…c394
3 touches
1 conflict
0xec82ec4a…caa5
0x065c9d…c394
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity