pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,424,553
← previous block
next block →
recent activity
Analyzing
Block #96,424,553
11 transactions · 9 stateful · 2026-08-16 07:00:07 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
#96,424,553
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
· blocks 1
#3
0x5acec890
#4
execFwdPositionOpsV2
#6
0x57368ddf
#7
execFwdPositionOpsV2
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x921a58d1…db22
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x003b6142…6bce
0x34b655…2a6f
2 touches
0 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x09775041…3e77
0x34b655…2a6f
2 touches
0 conflicts
0x0b31676d…7797
0x34b655…2a6f
2 touches
0 conflicts
0x0f2d78b1…7363
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
0x921a58d196…62db22
Audit this contract →
← previous block
·
next block →
recent activity