← previous blocknext block →recent activity
Analyzing
Block #73,318,163
14 transactions · 11 stateful · 2026-05-08 21:01:27 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,318,163 · 14 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
4w05w16w09w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x4d91e6c6…4b1e
0x065c9d…c394
3 touches
1 conflict
0xf87be8f7…16de
0xd32edf…ff58
3 touches
1 conflict
0x08eb87df…14c2
0x6657d1…8ccc
2 touches
0 conflicts
0x0fae6d99…3083
0x6657d1…8ccc
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
1 conflict on slot 0x0b390c6160…02dc07
Audit this contract →
← previous block·next block →recent activity