pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,653,330
12 transactions · 10 stateful · 2026-05-10 10:13:34 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,653,330 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w39w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0x004af5b6…fe80
0xd32edf…ff58
5 touches
3 conflicts
0x01edc834…d0c3
0x065c9d…c394
4 touches
1 conflict
0x80887490…ee87
0x065c9d…c394
3 touches
1 conflict
0xc4b9fee0…e374
0x065c9d…c394
3 touches
1 conflict
0x2fce48cf…84de
0x065c9d…c394
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 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: 0x2a68ba18…8e90c5
3 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity