pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,705,359
85 transactions · 59 stateful · 2026-05-10 16:04:36 UTC
Parallelism
84/100
Blocked
75%
Avg conflicts / tx
2.35
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #73,705,359 · 85 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w512w414w615w720w123w257w359w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
28 touches
91 conflicts
0xaa8a1c54…ead3
0x34b655…2a6f
18 touches
36 conflicts
0x76f6f8a9…47aa
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
12 touches
15 conflicts
0xd996735f…8733
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 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: 0xab35264b…1cfa38
91 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity