pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,920,918
71 transactions · 39 stateful · 2026-05-11 16:09:04 UTC
Parallelism
77/100
Blocked
74%
Avg conflicts / tx
2.48
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #73,920,918 · 71 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w010w111w212w324w326w438w542w452w855w1161w962w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8b1712f…0ced
0xd32edf…ff58
31 touches
120 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
16 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
14 touches
21 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
8 touches
6 conflicts
0x56a919c4…ab49
0xee8c0e…1242
8 touches
6 conflicts
0x00000000…0008
0xc363d0…1e32
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: 0xd32edf66…9fff58
120 conflicts on slot 0xe8b1712f76…670ced
Audit this contract →
← previous block·next block →recent activity