← previous blocknext block →recent activity
Analyzing
Block #73,334,764
11 transactions · 11 stateful · 2026-05-08 22:51:52 UTC
Parallelism
45/100
Blocked
45%
Avg conflicts / tx
1.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,334,764 · 11 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x610cc3a1…dae5
0x065c9d…c394
2 touches
0 conflicts
0xbdc141a2…e6fe
0x065c9d…c394
2 touches
0 conflicts
0xbece28da…8b3e
0x065c9d…c394
2 touches
0 conflicts
0xd21803ae…dfc4
0x065c9d…c394
2 touches
0 conflicts
0xea3e6cdd…f18f
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity