pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,288,063
44 transactions · 33 stateful · 2026-05-04 02:41:02 UTC
Parallelism
73/100
Blocked
70%
Avg conflicts / tx
1.82
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #72,288,063 · 44 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w08w19w210w311w412w014w117w118w221w022w123w224w330w331w241w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
10 touches
10 conflicts
0xbc6958b1…90af
0xd32edf…ff58
9 touches
10 conflicts
0xbe9d1d23…3de2
0x34b655…2a6f
8 touches
6 conflicts
0x475d29e4…3caf
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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: 0x34b6552d…112a6f
28 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity