← previous blocknext block →recent activity
Analyzing
Block #72,224,192
8 transactions · 8 stateful · 2026-05-03 19:31:43 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,224,192 · 8 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
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe094a7f…539c
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4cf53e20…329a
0x065c9d…c394
3 touches
1 conflict
0x682d6f68…d062
0x065c9d…c394
3 touches
1 conflict
0x3037b40c…60e4
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x512705a6…3930
0x065c9d…c394
2 touches
0 conflicts
0x575d8102…5793
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0xbe094a7f86…d8539c
Audit this contract →
← previous block·next block →recent activity