pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,658,359
53 transactions · 26 stateful · 2026-05-10 10:47:33 UTC
Parallelism
74/100
Blocked
69%
Avg conflicts / tx
1.83
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #73,658,359 · 53 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
1w02w13w24w35w410w511w613w714w815w916w1035w1036w1138w1242w1344w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4c0f5fb…ea5c
0xd32edf…ff58
27 touches
91 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x0a6cb118…4ca7
0x1b6862…e19c
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: 0xd32edf66…9fff58
91 conflicts on slot 0xf4c0f5fbe1…48ea5c
Audit this contract →
← previous block·next block →recent activity