pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,996,218
45 transactions · 39 stateful · 2026-04-28 03:07:44 UTC
Parallelism
80/100
Blocked
64%
Avg conflicts / tx
1.91
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #70,996,218 · 45 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
1w02w19w210w311w412w513w014w115w216w333w243w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
16 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xd11dc26e…59ab
0x34b655…2a6f
9 touches
10 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
8 touches
6 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
8 touches
6 conflicts
0xe75ce681…ba61
0x188d58…ea8e
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: 0xb857c13a…1a9be1
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity