pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,695,932
← previous block
next block →
recent activity
Analyzing
Block #82,695,932
12 transactions · 10 stateful · 2026-06-21 07:45:53 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,695,932
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x3f5c179b
#5
forward
#6
forward
#7
approve
#8
0x6a379729
#9
0x39435dac
· blocks 1
#11
0xc7e3ec2c
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1608e55b…3e0c
0x34b655…2a6f
4 touches
1 conflict
0x57be321f…fecc
0x34b655…2a6f
4 touches
1 conflict
0x725c0153…5f97
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x546d22…8146
2 touches
0 conflicts
0x00000000…003d
0x851145…3f07
2 touches
0 conflicts
0x934b15f1…b5a9
0x851145…3f07
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
0x1608e55b86…853e0c
Audit this contract →
← previous block
·
next block →
recent activity