← previous blocknext block →recent activity
Analyzing
Block #73,913,322
11 transactions · 8 stateful · 2026-05-11 15:18:21 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,913,322 · 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3da608b0…61dd
0x065c9d…c394
4 touches
1 conflict
0x1f6a4f8c…e9ae
0x065c9d…c394
2 touches
0 conflicts
0x5c637c06…c4fe
0x065c9d…c394
2 touches
0 conflicts
0xb3b3936c…b080
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
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 0xf537eaa0c6…3873c8
Audit this contract →
← previous block·next block →recent activity