pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,917,625
← previous block
next block →
recent activity
Analyzing
Block #73,917,625
8 transactions · 6 stateful · 2026-05-11 15:47:07 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,917,625
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x39435dac
· blocks 2
#3
setData
#4
0x6a01fa73
#7
0x39435dac
#5
0x39435dac
· blocks 1
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa15427f6…d932
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4829d008…e5fa
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x1a7e478a…37a5
0x34b655…2a6f
2 touches
0 conflicts
0x2a545780…c415
0x34b655…2a6f
2 touches
0 conflicts
0x3478a2fd…aca7
0x34b655…2a6f
2 touches
0 conflicts
0x367350ca…a8cd
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:
0x34b6552d…112a6f
3 conflicts on slot
0xa15427f6ca…8bd932
Audit this contract →
← previous block
·
next block →
recent activity