← previous blocknext block →recent activity
Analyzing
Block #73,867,242
11 transactions · 9 stateful · 2026-05-11 10:11:30 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,867,242 · 11 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
1w03w15w27w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86ab36b4…f4bd
0x065c9d…c394
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7f81fb82…633e
0x065c9d…c394
4 touches
1 conflict
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x47dee1e1…250e
0x699abc…6a3b
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 0x86ab36b454…88f4bd
Audit this contract →
← previous block·next block →recent activity