← previous blocknext block →recent activity
Analyzing
Block #73,693,850
16 transactions · 13 stateful · 2026-05-10 14:46:59 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,693,850 · 16 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
5w06w17w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0xffe7ff82…e30a
0xd32edf…ff58
3 touches
1 conflict
0x9cf12c64…b117
0x065c9d…c394
2 touches
0 conflicts
0xae69c125…2379
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0000
0x35aa76…fd64
2 touches
0 conflicts
0x00000000…0001
0x35aa76…fd64
2 touches
0 conflicts
0x00000000…0002
0x35aa76…fd64
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