← previous blocknext block →recent activity
Analyzing
Block #73,377,571
20 transactions · 17 stateful · 2026-05-09 03:36:37 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
1.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,377,571 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w28w310w311w412w513w414w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x22e295f5…1bef
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0x4e766fad…79a6
0xc8689a…ee79
4 touches
1 conflict
0x1a4b4152…0a08
0x8e764f…e322
4 touches
1 conflict
0x2e2214a9…fe0d
0x8e764f…e322
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x8e764f…e322
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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity