← previous blocknext block →recent activity
Analyzing
Block #73,744,793
22 transactions · 17 stateful · 2026-05-10 20:30:45 UTC
Parallelism
77/100
Blocked
29%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,744,793 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w09w114w217w318w420w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ac31945…2c72
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x946d865c…7c4a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0xcb45d9d6…cb85
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
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
6 conflicts on slot 0x0ac3194537…8f2c72
Audit this contract →
← previous block·next block →recent activity