pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,660,937
34 transactions · 24 stateful · 2026-05-10 11:04:51 UTC
Parallelism
59/100
Blocked
67%
Avg conflicts / tx
2.88
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #73,660,937 · 34 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
3w04w15w26w37w48w59w610w711w812w913w1014w1122w1225w1226w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06239abe…153f
0xd32edf…ff58
27 touches
91 conflicts
0xd59f6ed1…03e8
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x846f2172…fd54
0x0555e3…2b9c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
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 0x06239abe3f…62153f
Audit this contract →
← previous block·next block →recent activity