← previous blocknext block →recent activity
Analyzing
Block #73,989,885
10 transactions · 9 stateful · 2026-05-11 23:49:15 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,989,885 · 10 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
1w03w06w17w28w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf537eaa0…73c8
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xb9e53d21…28aa
0x065c9d…c394
4 touches
1 conflict
0x39c7674b…fd82
0x065c9d…c394
3 touches
1 conflict
0xc128b175…1174
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0xc0607737…a39e
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
3 conflicts on slot 0xf537eaa0c6…3873c8
Audit this contract →
← previous block·next block →recent activity