← previous blocknext block →recent activity
Analyzing
Block #73,990,137
13 transactions · 9 stateful · 2026-05-11 23:50:57 UTC
Parallelism
77/100
Blocked
22%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,990,137 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xc5b5128a…c5b2
0x065c9d…c394
4 touches
1 conflict
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x19c71b26…37ce
0x065c9d…c394
3 touches
1 conflict
0xc5093d48…dc9a
0x065c9d…c394
3 touches
1 conflict
0x2e4499b9…6d34
0x065c9d…c394
2 touches
0 conflicts
0x2ec36e63…e389
0x065c9d…c394
2 touches
0 conflicts
0x8c5da132…7723
0x065c9d…c394
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: MarginAccount
3 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity