pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,908,881
37 transactions · 30 stateful · 2026-04-27 17:26:03 UTC
Parallelism
89/100
Blocked
47%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #70,908,881 · 37 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
1w02w13w24w06w17w010w116w017w018w119w020w121w223w024w125w026w227w328w132w133w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
8 touches
6 conflicts
0xb9d2cf20…a668
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x181ed6ec…8003
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
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: 0x2a68ba18…8e90c5
6 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity