pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,041,807
57 transactions · 38 stateful · 2026-05-07 14:22:45 UTC
Parallelism
72/100
Blocked
58%
Avg conflicts / tx
2.37
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #73,041,807 · 57 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w19w014w015w116w224w126w327w428w532w633w734w835w936w1038w1139w1241w1342w955w1456w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf70705a…1726
0xd32edf…ff58
31 touches
120 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
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
120 conflicts on slot 0xaf70705a5a…7d1726
Audit this contract →
← previous block·next block →recent activity