pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,336,105
← previous block
next block →
recent activity
Analyzing
Block #84,336,105
11 transactions · 10 stateful · 2026-06-28 22:12:59 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,336,105
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
forward
#5
execFwdPositionOps
· blocks 1
#6
setData
#7
0x32366535
#8
execOrders
· blocks 2
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x807bf45f…5016
0x34b655…2a6f
4 touches
1 conflict
0x049cca71…b102
0x34b655…2a6f
4 touches
1 conflict
0xf6a1f3a2…0b36
0x34b655…2a6f
3 touches
1 conflict
0xcdc2f4e6…812f
0x065c9d…c394
2 touches
0 conflicts
0xe75cebb6…6b36
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity