← previous blocknext block →recent activity
Analyzing
Block #72,994,451
13 transactions · 10 stateful · 2026-05-07 09:07:45 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,994,451 · 13 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
3w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x70b2f813…783c
0x2a68ba…90c5
8 touches
6 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…000b
0x6ca43f…c331
8 touches
6 conflicts
0x0175b7a6…1dba
0x6ca43f…c331
8 touches
6 conflicts
0x1a4b4152…0a08
0x6ca43f…c331
8 touches
6 conflicts
0xe7535190…5a0f
0x6ca43f…c331
8 touches
6 conflicts
0xe94e77ab…f017
0x6ca43f…c331
8 touches
6 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity