← previous blocknext block →recent activity
Analyzing
Block #73,029,440
21 transactions · 19 stateful · 2026-05-07 13:00:26 UTC
Parallelism
62/100
Blocked
53%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,029,440 · 21 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
1w02w13w05w16w27w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
12 touches
15 conflicts
0x0b390c61…dc07
0x065c9d…c394
10 touches
10 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
8 touches
6 conflicts
0x24cfa19b…8fc9
0x065c9d…c394
7 touches
6 conflicts
0xbb6ec1c8…fc9f
0x065c9d…c394
7 touches
6 conflicts
0x1045386d…cb8d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity