pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,687,853
← previous block
next block →
recent activity
Analyzing
Block #82,687,853
11 transactions · 9 stateful · 2026-06-21 06:52:01 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,687,853
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
batchCancelOrders
#5
0x35a776ca
#6
placeBet
#7
setData
#8
execOrders
· blocks 1
#10
0xc7e3ec2c
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x83101aae…77f1
0x065c9d…c394
2 touches
0 conflicts
0xb2f83d7c…3a7d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0069
0x07414c…13ab
2 touches
0 conflicts
0x557cd4fa…228c
0x2a68ba…90c5
2 touches
0 conflicts
0x4c3db33b…c5bc
0x754704…b603
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
0xfadc118dc2…025d64
Audit this contract →
← previous block
·
next block →
recent activity