← previous blocknext block →recent activity
Analyzing
Block #73,861,048
9 transactions · 8 stateful · 2026-05-11 09:30:08 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,861,048 · 9 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
1w03w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x943bf267…fd17
0x754704…b603
4 touches
1 conflict
0x1c354dc0…96de
0x754704…b603
4 touches
1 conflict
0xf91b744e…9117
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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 0x22e295f5d8…ac1bef
Audit this contract →
← previous block·next block →recent activity