pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,748,892
25 transactions · 16 stateful · 2026-05-10 20:58:26 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,748,892 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fb0d285…13e5
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x00000000…0000
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…0002
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…0004
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…000c
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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: 0xd32edf66…9fff58
28 conflicts on slot 0x6fb0d285d7…1513e5
Audit this contract →
← previous block·next block →recent activity