← previous blocknext block →recent activity
Analyzing
Block #73,924,866
31 transactions · 26 stateful · 2026-05-11 16:35:20 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.55
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #73,924,866 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w17w111w012w113w114w215w216w317w418w520w521w622w723w824w925w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0x6f08361d…bda6
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x7aae960e…633f
0xd32edf…ff58
9 touches
10 conflicts
0xf537eaa0…73c8
0x065c9d…c394
8 touches
6 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
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity