pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,043,076
48 transactions · 35 stateful · 2026-05-07 14:31:14 UTC
Parallelism
79/100
Blocked
66%
Avg conflicts / tx
1.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,043,076 · 48 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w19w110w011w113w015w216w318w120w221w025w130w231w332w433w534w635w738w139w840w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72c8c2eb…7e15
0xd32edf…ff58
17 touches
36 conflicts
0x7f189cf6…afab
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
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
36 conflicts on slot 0x72c8c2eb86…067e15
Audit this contract →
← previous block·next block →recent activity