pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,343,741
55 transactions · 32 stateful · 2026-05-08 23:51:35 UTC
Parallelism
76/100
Blocked
66%
Avg conflicts / tx
1.76
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,343,741 · 55 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w825w237w938w1042w1144w346w554w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd54046eb…da3f
0xd32edf…ff58
25 touches
78 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xf537eaa0…73c8
0x065c9d…c394
8 touches
6 conflicts
0xd025d7d7…f05a
0x3bd359…433a
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
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: 0xd32edf66…9fff58
78 conflicts on slot 0xd54046eb2f…87da3f
Audit this contract →
← previous block·next block →recent activity