pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,480,971
17 transactions · 16 stateful · 2026-05-09 15:04:41 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,480,971 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w09w010w011w115w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba5743c7…21bf
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x6e780c33…3e00
0xd32edf…ff58
7 touches
6 conflicts
0x1acaa26f…7b77
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
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: 0x1b68626d…2de19c
6 conflicts on slot 0xba5743c7a6…7321bf
Audit this contract →
← previous block·next block →recent activity