pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,708,205
← previous block
next block →
recent activity
Analyzing
Block #82,708,205
10 transactions · 7 stateful · 2026-06-21 09:07:46 UTC
Parallelism
80
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,708,205
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb264ae19
· blocks 1
#3
0xab083028
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x226fd1…1655
#9
0xc7e3ec2c
#2
0xb264ae19
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38b5b2ce…c5bb
0xfa32f9…f3f0
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0x9926923a…bad3
0x754704…b603
4 touches
1 conflict
0xb07a35ae…9f83
0x754704…b603
4 touches
1 conflict
0xbd8ffcea…d2db
0x754704…b603
4 touches
1 conflict
0xd95b1a11…4e4d
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
4 touches
1 conflict
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:
0xfa32f9ec…fef3f0
1 conflict on slot
0x38b5b2ceac…4cc5bb
Audit this contract →
← previous block
·
next block →
recent activity