pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,624,708
← previous block
next block →
recent activity
Analyzing
Block #96,624,708
14 transactions · 8 stateful · 2026-08-16 23:47:08 UTC
Parallelism
86
/100
Blocked
13
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,624,708
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4f819052
· blocks 1
#2
0x00a41485
#4
0x05ee6a22
#5
execOrders
#6
execPerpOps
#7
0x62be7533
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
#12
transferWithAuthorization
#13
setData
#3
0x50a0b275
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x00000000…0003
0x834d94…8555
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
4 touches
1 conflict
0x00000000…0000
0x850662…52d0
4 touches
1 conflict
0x00000000…0002
0x850662…52d0
4 touches
1 conflict
0x00000000…0004
0x850662…52d0
4 touches
1 conflict
0x63f5c02f…6853
0x3bd359…433a
4 touches
1 conflict
0xb1632c2f…d991
0x0a3323…0a3c
4 touches
1 conflict
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:
0x834d94a0…2e8555
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity