pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,041,782
54 transactions · 44 stateful · 2026-05-07 14:22:35 UTC
Parallelism
76/100
Blocked
75%
Avg conflicts / tx
2.11
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,041,782 · 54 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
1w02w13w25w07w28w39w312w413w414w116w317w418w319w527w728w834w235w336w437w539w641w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
18 touches
36 conflicts
0x07d301ff…de58
0xd32edf…ff58
15 touches
28 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
14 touches
21 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
14 touches
21 conflicts
0x7f189cf6…afab
0x065c9d…c394
14 touches
21 conflicts
0xf4730a2d…3538
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xd574ca…7ab1
8 touches
6 conflicts
0x70b2f813…783c
0x2a68ba…90c5
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: 0x065c9d28…a9c394
36 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity