pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,669,346
32 transactions · 28 stateful · 2026-05-10 12:01:37 UTC
Parallelism
75/100
Blocked
46%
Avg conflicts / tx
1.09
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,669,346 · 32 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w010w220w221w322w423w224w326w527w628w731w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x529acb6a…fcc6
0x065c9d…c394
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x0ac31945…2c72
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
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: 0x065c9d28…a9c394
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity