pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,171,530
← previous block
next block →
recent activity
Analyzing
Block #72,171,530
8 transactions · 8 stateful · 2026-05-03 13:37:55 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,171,530
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xfa88789d
· blocks 2
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x3f5c179b
#7
0x69f7502a
#2
0xfa88789d
· blocks 1
#3
0xfa88789d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b936aa5…05e5
0x141b1d…9583
6 touches
3 conflicts
0x00000000…0003
0x2ae0cf…3d4e
6 touches
3 conflicts
0x00000000…0001
0x67d1be…196f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x02e0c10f…a495
0x065c9d…c394
2 touches
0 conflicts
0x0bfaf86e…2495
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0002
0x08dd3d…a583
2 touches
0 conflicts
0xff9eec93…1598
0x08dd3d…a583
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:
0x141b1d9e…ab9583
3 conflicts on slot
0x2b936aa586…6905e5
Audit this contract →
← previous block
·
next block →
recent activity