← previous blocknext block →recent activity
Analyzing
Block #73,795,940
10 transactions · 10 stateful · 2026-05-11 02:15:53 UTC
Parallelism
40/100
Blocked
60%
Avg conflicts / tx
2.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,795,940 · 10 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
1w02w03w14w15w26w37w48w5
- 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
8 touches
6 conflicts
0x0ac31945…2c72
0x065c9d…c394
8 touches
6 conflicts
0x529acb6a…fcc6
0x065c9d…c394
2 touches
0 conflicts
0x8fcdd619…3d9b
0x065c9d…c394
2 touches
0 conflicts
0xdd6eb39d…bf3a
0x065c9d…c394
2 touches
0 conflicts
0xea147538…1923
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