pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,696,513
← previous block
next block →
recent activity
Analyzing
Block #82,696,513
7 transactions · 5 stateful · 2026-06-21 07:49:45 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,696,513
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
setData
#4
0xae531b…e0b4
#5
0x39435dac
· blocks 1
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14588173…210c
0x34b655…2a6f
4 touches
1 conflict
0xb3c96942…f0fc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x588da1c1…6ae5
0x34b655…2a6f
3 touches
1 conflict
0x090fde28…e675
0x34b655…2a6f
2 touches
0 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
2 touches
0 conflicts
0x4e1f9ab2…7f51
0x34b655…2a6f
2 touches
0 conflicts
0x62db95d4…351c
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
0x1458817348…8e210c
Audit this contract →
← previous block
·
next block →
recent activity