pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,595,172
← previous block
next block →
recent activity
Analyzing
Block #96,595,172
8 transactions · 7 stateful · 2026-08-16 21:18:35 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,595,172
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
execOrders
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
#6
updateDataFeedsValuesPartial
#7
setData
#3
execFwdPositionOpsV2
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
0xa5c8cbd0…4891
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0460135c…98fd
0x34b655…2a6f
2 touches
0 conflicts
0x09385be7…8d02
0x34b655…2a6f
2 touches
0 conflicts
0x0d6a6489…89e3
0x34b655…2a6f
2 touches
0 conflicts
0x33540876…1ec1
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
0xa5c8cbd0c2…b54891
Audit this contract →
← previous block
·
next block →
recent activity