pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,273,543
47 transactions · 33 stateful · 2026-05-08 16:04:33 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
1.34
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,273,543 · 47 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w314w415w130w531w632w733w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55597b08…55c7
0xd32edf…ff58
17 touches
36 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
12 touches
15 conflicts
0x0a6cb118…4ca7
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001c
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002c
0x1b6862…e19c
12 touches
15 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
36 conflicts on slot 0x55597b082c…f255c7
Audit this contract →
← previous block·next block →recent activity