pev.One block, wave by wave
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,996,390
16 transactions · 16 stateful · 2026-04-28 03:08:53 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #70,996,390 · 16 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
2w03w04w15w17w09w010w111w212w113w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0xffe431af…8faa
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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: 0x2a68ba18…8e90c5
10 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity