← previous blocknext block →recent activity
Analyzing
Block #73,215,393
11 transactions · 10 stateful · 2026-05-08 09:37:42 UTC
Parallelism
55/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,215,393 · 11 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
1w02w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x738ac99d…1bad
0xd32edf…ff58
3 touches
1 conflict
0x1bc243c5…7100
0x065c9d…c394
2 touches
0 conflicts
0x289ec630…f18b
0x065c9d…c394
2 touches
0 conflicts
0x34e46721…2b80
0x065c9d…c394
2 touches
0 conflicts
0x69e60a1a…f4ad
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: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity