pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,497,112
42 transactions · 37 stateful · 2026-05-05 01:54:02 UTC
Parallelism
86/100
Blocked
59%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,497,112 · 42 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w17w08w012w213w215w016w117w218w320w021w122w223w324w425w526w127w229w132w133w235w240w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xf3981be5…2c47
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x7e9d3a…9fda
8 touches
6 conflicts
0x8a35acfb…d1ae
0x8d66a4…3095
8 touches
6 conflicts
0xf9f733a6…57bd
0xd32edf…ff58
7 touches
6 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
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: 0x34b6552d…112a6f
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity