pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,986,247
42 transactions · 38 stateful · 2026-04-28 02:01:19 UTC
Parallelism
74/100
Blocked
63%
Avg conflicts / tx
1.74
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #70,986,247 · 42 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w09w113w014w115w216w317w418w521w225w326w340w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
16 touches
28 conflicts
0x9551b342…ffaf
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x24968e6d…0132
0x065c9d…c394
10 touches
10 conflicts
0xbbee74c2…567a
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x131a2e…0da9
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 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
28 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity