pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,539,117
← previous block
next block →
recent activity
Analyzing
Block #95,539,117
11 transactions · 10 stateful · 2026-08-13 04:45:06 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,539,117
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updatePrices
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a7d4c49
#8
setData
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c7c65d0…0b52
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x0a255626…48e1
0x34b655…2a6f
2 touches
0 conflicts
0x177c052e…67cb
0x34b655…2a6f
2 touches
0 conflicts
0x198ecc9b…e4cd
0x34b655…2a6f
2 touches
0 conflicts
0x23a85fab…daaf
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
0x3c7c65d0e6…a00b52
Audit this contract →
← previous block
·
next block →
recent activity