pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,597,662
88 transactions · 43 stateful · 2026-05-10 04:00:24 UTC
Parallelism
80/100
Blocked
79%
Avg conflicts / tx
2
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #73,597,662 · 88 txs across 18 waves · depth 18
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
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w010w011w118w120w127w242w143w258w259w360w461w562w663w764w167w868w969w1070w1171w1273w1374w1476w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdda695e1…bc84
0xd32edf…ff58
33 touches
136 conflicts
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
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
136 conflicts on slot 0xdda695e199…28bc84
Audit this contract →
← previous block·next block →recent activity