pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,655,006
← previous block
next block →
recent activity
Analyzing
Block #83,655,006
9 transactions · 9 stateful · 2026-06-25 18:33:18 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
#83,655,006
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
· blocks 2
#2
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
forward
#6
setData
#8
0xc7e3ec2c
#3
0x0f6795d9
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b7c45d…9d5a
0x34b655…2a6f
6 touches
3 conflicts
0x47d04781…2b47
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x1c48b3ac…a03c
0x34b655…2a6f
2 touches
0 conflicts
0x487922c6…dbd2
0x34b655…2a6f
2 touches
0 conflicts
0x59201bcc…e576
0x34b655…2a6f
2 touches
0 conflicts
0x675e5671…b2bb
0x34b655…2a6f
2 touches
0 conflicts
0x8e5cc690…b06b
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
3 conflicts on slot
0xb6b7c45de7…c49d5a
Audit this contract →
← previous block
·
next block →
recent activity