pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,700,417
← previous block
next block →
recent activity
Analyzing
Block #96,700,417
12 transactions · 8 stateful · 2026-08-17 06:07:55 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,700,417
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
execOrders
#4
execute
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
handleOps
· blocks 1
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
setData
#8
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0659a3f…90d9
0x000000…a032
4 touches
1 conflict
0x00000000…000b
0x754704…b603
4 touches
1 conflict
0x34b1e500…7687
0x754704…b603
4 touches
1 conflict
0x00000000…000b
0x78999c…f371
4 touches
1 conflict
0x00000000…000f
0x78999c…f371
4 touches
1 conflict
0x10d80fee…dbda
0x2b46c0…1669
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
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:
0x00000000…7da032
1 conflict on slot
0xe0659a3f75…9f90d9
Audit this contract →
← previous block
·
next block →
recent activity