← previous blocknext block →recent activity
Analyzing
Block #73,503,415
11 transactions · 8 stateful · 2026-05-09 17:34:11 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,503,415 · 11 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
1w02w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xf92b6c60…f499
0x065c9d…c394
4 touches
1 conflict
0x6a7e4bfd…29d4
0x065c9d…c394
3 touches
1 conflict
0x9c5522d7…00e3
0x065c9d…c394
2 touches
0 conflicts
0xf70e64bd…6d49
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity