← previous blocknext block →recent activity
Analyzing
Block #73,990,267
11 transactions · 9 stateful · 2026-05-11 23:51:49 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,990,267 · 11 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
1w05w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x11e6ab21…2d0b
0x065c9d…c394
2 touches
0 conflicts
0x80a76be1…ea2b
0x065c9d…c394
2 touches
0 conflicts
0xa88f3bb9…a1ed
0x065c9d…c394
2 touches
0 conflicts
0xba1a5343…70fc
0x065c9d…c394
2 touches
0 conflicts
0xc787c16e…6f19
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