pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,631,592
← previous block
next block →
recent activity
Analyzing
Block #81,631,592
9 transactions · 9 stateful · 2026-06-16 09:22:57 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,631,592
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x39435dac
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0xa09e9040
#6
0x23afbff3
#7
setData
#3
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41be9e75…9773
0x34b655…2a6f
6 touches
3 conflicts
0xc0ee8ce1…0778
0x34b655…2a6f
6 touches
3 conflicts
0xddfaf3dd…41b4
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x9ab652e0…6bca
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0xd17679d9…313f
0x34b655…2a6f
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:
Perpl
3 conflicts on slot
0x41be9e7517…b39773
Audit this contract →
← previous block
·
next block →
recent activity