← previous blocknext block →recent activity
Analyzing
Block #74,241,378
24 transactions · 21 stateful · 2026-05-13 03:43:30 UTC
Parallelism
58/100
Blocked
48%
Avg conflicts / tx
1.83
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,241,378 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w010w211w316w417w518w619w720w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
18 touches
36 conflicts
0x8e66da19…66b6
0x065c9d…c394
8 touches
6 conflicts
0x2a354a63…0515
0x065c9d…c394
8 touches
6 conflicts
0x765c236f…ff45
0x2a68ba…90c5
8 touches
6 conflicts
0xd25997d0…a68a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
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
36 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity