pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,892,302
35 transactions · 28 stateful · 2026-04-27 15:35:38 UTC
Parallelism
74/100
Blocked
54%
Avg conflicts / tx
0.97
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #70,892,302 · 35 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w110w011w112w213w314w416w017w120w222w223w324w425w529w530w632w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x7b7bcac3…8fbf
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1b0
0x8d66a4…3095
6 touches
3 conflicts
0xf823e97f…2ee6
0x065c9d…c394
6 touches
3 conflicts
0x1c913164…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0x3c83275e…d7c2
0x34b655…2a6f
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
10 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity