pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,021,829
← previous block
next block →
recent activity
Analyzing
Block #95,021,829
15 transactions · 13 stateful · 2026-08-11 09:08:48 UTC
Parallelism
80
/100
Blocked
15
%
Avg conflicts / tx
0.13
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,021,829
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
· blocks 1
#4
updatePrices
#5
0x5acec890
#6
execOrders
#7
batchUpdate
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
transfer
#11
setData
#12
execute
#13
0x59558d29
#14
execOrders
#2
execOrder
· blocks 1
#3
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0d378dc8…5e93
0x34b655…2a6f
2 touches
0 conflicts
0x2a1544ad…9f70
0x34b655…2a6f
2 touches
0 conflicts
0x45321d59…fc8a
0x34b655…2a6f
2 touches
0 conflicts
0x480463fd…bd45
0x34b655…2a6f
2 touches
0 conflicts
0x5a19ef35…dc70
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
0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block
·
next block →
recent activity