pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,933,786
← previous block
next block →
recent activity
Analyzing
Block #83,933,786
12 transactions · 10 stateful · 2026-06-27 01:32:54 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
#83,933,786
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
#2
updateDataFeedsValuesPartial
#3
0x98717539
· blocks 1
#5
execFwdPositionOps
#6
forward
#7
execFwdPositionOps
#8
0x6a3f28be
#9
0x90c647…c5f1
#10
setData
#11
execOrders
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0x76477ddf…b8f8
0xc8689a…ee79
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2f22eea9…3cec
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x0020cef4…3ffc
0x34b655…2a6f
2 touches
0 conflicts
0x6acc4afc…e7db
0x34b655…2a6f
2 touches
0 conflicts
0x785889c9…0603
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
0xa92c87634b…146d7f
Audit this contract →
← previous block
·
next block →
recent activity