← previous blocknext block →recent activity
Analyzing
Block #71,700,882
10 transactions · 10 stateful · 2026-05-01 09:24:12 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,700,882 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c0b9f32…5938
0x065c9d…c394
5 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x019001cf…7a2d
0xd32edf…ff58
3 touches
1 conflict
0x3a3097d7…2ab6
0x1b6862…e19c
2 touches
0 conflicts
0x12530975…a089
0x3bd359…433a
2 touches
0 conflicts
0x4bef88e0…eaca
0x3bd359…433a
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 0x4c0b9f3209…b15938
Audit this contract →
← previous block·next block →recent activity