← previous blocknext block →recent activity
Analyzing
Block #73,042,461
15 transactions · 12 stateful · 2026-05-07 14:27:07 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,042,461 · 15 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
1w06w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0xa2eb8d39…d7cd
0xd32edf…ff58
3 touches
1 conflict
0x61337b97…e0ff
0x065c9d…c394
2 touches
0 conflicts
0x70b2f813…783c
0x2a68ba…90c5
2 touches
0 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
2 touches
0 conflicts
0x0f9b918b…212d
0x34b655…2a6f
2 touches
0 conflicts
0x1956cea3…dc45
0x34b655…2a6f
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 0xce7bfe5ef1…205e58
Audit this contract →
← previous block·next block →recent activity