pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,271,178
← previous block
next block →
recent activity
Analyzing
Block #72,271,178
10 transactions · 8 stateful · 2026-05-04 00:47:31 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,271,178
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
· blocks 1
#3
0x3f5c179b
#4
updateDataFeedsValuesPartial
#5
0x6df9e92b
#6
execute
#7
setData
#8
0x4ee773…11ef
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x005fb969…2d97
0x34b655…2a6f
2 touches
0 conflicts
0x0520da1d…c88e
0x34b655…2a6f
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x104887dc…9894
0x34b655…2a6f
2 touches
0 conflicts
0x1608635c…d25d
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
0x8c49c85c3e…afee96
Audit this contract →
← previous block
·
next block →
recent activity