← previous blocknext block →recent activity
Analyzing
Block #72,309,508
23 transactions · 16 stateful · 2026-05-04 05:04:19 UTC
Parallelism
91/100
Blocked
25%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,309,508 · 23 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
9w011w012w113w014w115w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52be7e7e…8219
0x065c9d…c394
4 touches
1 conflict
0xf823e97f…2ee6
0x065c9d…c394
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
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x3254d19b…f714
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity