← previous blocknext block →recent activity
Analyzing
Block #71,330,263
8 transactions · 8 stateful · 2026-04-29 16:11:46 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,330,263 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x278b8c29…a997
0x065c9d…c394
2 touches
0 conflicts
0x46c16654…5478
0x065c9d…c394
2 touches
0 conflicts
0x481416bd…e16a
0x065c9d…c394
2 touches
0 conflicts
0xc54648f5…0e24
0x065c9d…c394
2 touches
0 conflicts
0x5ba9bdf0…512d
0x0dfbc6…7777
2 touches
0 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity