pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,041,958
20 transactions · 20 stateful · 2026-05-07 14:23:46 UTC
Parallelism
35/100
Blocked
70%
Avg conflicts / tx
4.05
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,041,958 · 20 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
26 touches
78 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1aa
0x8d66a4…3095
6 touches
3 conflicts
0x9d1bb389…c7d9
0x8d66a4…3095
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x2b083a11…6a54
0x34b655…2a6f
2 touches
0 conflicts
0x3702b140…97ea
0x34b655…2a6f
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: 0xd574cae5…037ab1
78 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity