pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,201,582
80 transactions · 52 stateful · 2026-05-08 08:05:54 UTC
Parallelism
84/100
Blocked
71%
Avg conflicts / tx
1.71
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,201,582 · 80 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
1w04w07w014w117w222w323w324w427w128w230w335w337w438w539w365w967w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1673d4d4…3524
0xd32edf…ff58
21 touches
55 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x3b8ffd61…f3ad
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0xf91b744e…9117
0x754704…b603
10 touches
10 conflicts
0x1c354dc0…96de
0x754704…b603
10 touches
10 conflicts
0x6af306bb…2e81
0x3bd359…433a
10 touches
10 conflicts
0x01e7b865…6e6d
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: 0xd32edf66…9fff58
55 conflicts on slot 0x1673d4d40e…6e3524
Audit this contract →
← previous block·next block →recent activity