pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,092,289
58 transactions · 44 stateful · 2026-04-28 13:47:26 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
1.5
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #71,092,289 · 58 txs across 14 waves · depth 14
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
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w28w010w111w022w024w125w226w327w428w529w632w733w834w935w1037w138w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0x1c913164…5c2e
0x34b655…2a6f
14 touches
21 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
10 touches
10 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
10 touches
10 conflicts
0xf763cad4…23f1
0x34b655…2a6f
10 touches
10 conflicts
0x50059a18…9b7b
0x34b655…2a6f
10 touches
10 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
8 touches
6 conflicts
0x62d6e82b…a750
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
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity