pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,047,434
← previous block
next block →
recent activity
Analyzing
Block #73,047,434
8 transactions · 7 stateful · 2026-05-07 15:00:15 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,047,434
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0xeffdedb0
#5
setData
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
4 touches
1 conflict
0x660b3c19…372a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x13619ff6…9c52
0x34b655…2a6f
2 touches
0 conflicts
0x251861eb…78fd
0x34b655…2a6f
2 touches
0 conflicts
0x3817764d…242b
0x34b655…2a6f
2 touches
0 conflicts
0x3b8ffd61…f3ad
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:
Perpl
1 conflict on slot
0x388e001a16…e57e04
Audit this contract →
← previous block
·
next block →
recent activity