← previous blocknext block →recent activity
Analyzing
Block #73,962,940
25 transactions · 19 stateful · 2026-05-11 20:48:34 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
1.2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,962,940 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w010w411w512w613w714w823w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x6f08361d…bda6
0x065c9d…c394
8 touches
6 conflicts
0xf537eaa0…73c8
0x065c9d…c394
8 touches
6 conflicts
0x84c5474e…0944
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xd1480c90…ae06
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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