pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,571,118
← previous block
next block →
recent activity
Analyzing
Block #82,571,118
11 transactions · 10 stateful · 2026-06-20 17:49:49 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,571,118
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrder
#3
addSellOrder
· blocks 1
#5
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#8
execFwdPositionOps
#9
0x6a36d334
#10
setData
#4
batchCancelOrders
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0x733b1193…6e08
0x065c9d…c394
4 touches
1 conflict
0x10d8d4e9…cd95
0x065c9d…c394
3 touches
1 conflict
0xc2968875…ca37
0x065c9d…c394
3 touches
1 conflict
0x23a320fb…cbd7
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x5a19ef35…dc70
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
0x8b305a3b6b…0c1c35
Audit this contract →
← previous block
·
next block →
recent activity