← previous blocknext block →recent activity
Analyzing
Block #73,674,068
14 transactions · 14 stateful · 2026-05-10 12:33:31 UTC
Parallelism
43/100
Blocked
64%
Avg conflicts / tx
2.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,674,068 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w47w08w19w210w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x046a928e…0012
0x2a68ba…90c5
12 touches
15 conflicts
0x529acb6a…fcc6
0x065c9d…c394
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x0ac31945…2c72
0x065c9d…c394
8 touches
6 conflicts
0xa8830549…59eb
0x065c9d…c394
3 touches
1 conflict
0xd00f6663…94f7
0x065c9d…c394
3 touches
1 conflict
0x558b180e…9189
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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity