pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,223,017
← previous block
next block →
recent activity
Analyzing
Block #82,223,017
12 transactions · 7 stateful · 2026-06-19 03:07:09 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,223,017
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
#3
forward
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0x6a34b2d5
#8
setData
#9
0xdcd425…84dd
#10
0x55a49d…07cc
#11
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x184b47c9…59df
0x34b655…2a6f
2 touches
0 conflicts
0x3355228b…a9fe
0x34b655…2a6f
2 touches
0 conflicts
0x427c9fc4…5cee
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0x793aa64d0d…fdb09d
Audit this contract →
← previous block
·
next block →
recent activity