pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,868,257
30 transactions · 28 stateful · 2026-05-11 10:18:15 UTC
Parallelism
30/100
Blocked
82%
Avg conflicts / tx
7.13
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #73,868,257 · 30 txs across 21 waves · depth 21
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
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w610w711w812w913w1014w1115w1216w1317w1418w1519w1620w1721w1822w1923w2024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
42 touches
210 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb159af88…a9e7
0x065c9d…c394
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
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: 0x1414f3ba…045137
210 conflicts on slot 0x0000000000…000007
Audit this contract →
← previous block·next block →recent activity