pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,239,374
37 transactions · 32 stateful · 2026-04-29 06:06:30 UTC
Parallelism
65/100
Blocked
66%
Avg conflicts / tx
2.32
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #71,239,374 · 37 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w19w110w011w112w214w315w416w517w618w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee110ef…8394
0x34b655…2a6f
16 touches
28 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xb857c1…9be1
14 touches
21 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
10 touches
10 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
10 touches
10 conflicts
0xafd59af5…5257
0xc8689a…ee79
10 touches
10 conflicts
0x2484cc15…5afc
0x34b655…2a6f
10 touches
10 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 0x7ee110efcf…e68394
Audit this contract →
← previous block·next block →recent activity