pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,212,060
← previous block
next block →
recent activity
Analyzing
Block #73,212,060
8 transactions · 7 stateful · 2026-05-08 09:15:30 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,212,060
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0xeffdedb0
#6
setData
#7
0x39435dac
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87a380d9…2d04
0x34b655…2a6f
4 touches
1 conflict
0x8c752560…599d
0x34b655…2a6f
4 touches
1 conflict
0x3b3a5945…10d0
0x34b655…2a6f
4 touches
1 conflict
0x9e52eba4…6b28
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
2 touches
0 conflicts
0x388e001a…7e04
0x34b655…2a6f
2 touches
0 conflicts
0x61ad45b1…15ac
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
0x87a380d9ab…192d04
Audit this contract →
← previous block
·
next block →
recent activity