← previous blocknext block →recent activity
Analyzing
Block #73,948,654
21 transactions · 17 stateful · 2026-05-11 19:13:35 UTC
Parallelism
43/100
Blocked
76%
Avg conflicts / tx
2.48
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #73,948,654 · 21 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w312w513w614w515w716w817w918w1019w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0xf537eaa0…73c8
0x065c9d…c394
14 touches
21 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x6f08361d…bda6
0x065c9d…c394
10 touches
10 conflicts
0x3595e21e…052b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
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