pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,502,396
41 transactions · 35 stateful · 2026-05-09 17:27:22 UTC
Parallelism
71/100
Blocked
77%
Avg conflicts / tx
1.73
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #73,502,396 · 41 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w36w08w110w211w413w314w015w116w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd59af5…5257
0xc8689a…ee79
14 touches
21 conflicts
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x7b50a82b…f53d
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
8 touches
6 conflicts
0x157b6348…8604
0x34b655…2a6f
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 touches
6 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: 0xc8689a47…62ee79
21 conflicts on slot 0xafd59af545…b35257
Audit this contract →
← previous block·next block →recent activity