← previous blocknext block →recent activity
Analyzing
Block #72,928,992
16 transactions · 13 stateful · 2026-05-07 01:52:03 UTC
Parallelism
75/100
Blocked
54%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,928,992 · 16 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
1w02w13w04w16w27w38w09w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2a354a63…0515
0x065c9d…c394
6 touches
3 conflicts
0x9041b928…1c3f
0xd32edf…ff58
5 touches
3 conflicts
0xde40ebb1…af72
0x065c9d…c394
5 touches
3 conflicts
0x8e66da19…66b6
0x065c9d…c394
4 touches
1 conflict
0xf2a51df3…dac4
0x065c9d…c394
4 touches
1 conflict
0xf7acd433…c38d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity