pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,267,295
49 transactions · 35 stateful · 2026-05-04 00:21:26 UTC
Parallelism
80/100
Blocked
63%
Avg conflicts / tx
1.35
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #72,267,295 · 49 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w17w110w213w214w016w122w023w224w125w229w335w436w537w638w740w841w342w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ac4d8fb…b0de
0xd32edf…ff58
19 touches
45 conflicts
0x41755291…977f
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x47b807a2…3307
0x065c9d…c394
6 touches
3 conflicts
0xbf04f37d…85f2
0x2a68ba…90c5
6 touches
3 conflicts
0x801a6e57…d85c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfbe161dd…757b
0x3bd359…433a
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: 0xd32edf66…9fff58
45 conflicts on slot 0x3ac4d8fbb4…3fb0de
Audit this contract →
← previous block·next block →recent activity