← previous blocknext block →recent activity
Analyzing
Block #71,046,048
18 transactions · 14 stateful · 2026-04-28 08:39:23 UTC
Parallelism
72/100
Blocked
57%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,046,048 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w011w212w213w314w315w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0xba5743c7…21c6
0x1b6862…e19c
6 touches
3 conflicts
0x6e1a48f4…33aa
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity