← previous blocknext block →recent activity
Analyzing
Block #72,233,873
10 transactions · 9 stateful · 2026-05-03 20:36:47 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,233,873 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x74e71984…ae90
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x92c3c9e1…34eb
0x065c9d…c394
4 touches
1 conflict
0xd8d59b0c…1d0b
0x065c9d…c394
4 touches
1 conflict
0x8bb38724…ec6d
0x065c9d…c394
3 touches
1 conflict
0x8bb38724…ec6e
0x065c9d…c394
3 touches
1 conflict
0x28a090db…05d3
0xd32edf…ff58
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: USDC (USDC)
1 conflict on slot 0xa1087a5ca6…0a66c4
Audit this contract →
← previous block·next block →recent activity