← previous blocknext block →recent activity
Analyzing
Block #73,971,299
10 transactions · 9 stateful · 2026-05-11 21:44:19 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,971,299 · 10 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
1w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda655e6f…fbb1
0x065c9d…c394
4 touches
1 conflict
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0x6449082b…910b
0x065c9d…c394
3 touches
1 conflict
0x92080797…d5e8
0x065c9d…c394
3 touches
1 conflict
0x3c16c902…2961
0x065c9d…c394
2 touches
0 conflicts
0x512973f9…9731
0x065c9d…c394
2 touches
0 conflicts
0x6062b9d1…6172
0x065c9d…c394
2 touches
0 conflicts
0x71dfffb9…1c1b
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 0xda655e6f87…3afbb1
Audit this contract →
← previous block·next block →recent activity