pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,654,788
50 transactions · 35 stateful · 2026-05-15 01:42:37 UTC
Parallelism
84/100
Blocked
60%
Avg conflicts / tx
1.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,654,788 · 50 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w07w08w014w115w121w022w224w125w026w133w134w235w336w437w541w642w244w746w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002b6640…5dec
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0xf91b744e…9117
0x754704…b603
8 touches
6 conflicts
0xbad68552…e6bf
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x6af306bb…2e81
0x3bd359…433a
8 touches
6 conflicts
0x1c354dc0…96de
0x754704…b603
8 touches
6 conflicts
0xd98b3c10…67b8
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: 0xd32edf66…9fff58
28 conflicts on slot 0x002b66407f…d35dec
Audit this contract →
← previous block·next block →recent activity