pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,389,917
← previous block
next block →
recent activity
Analyzing
Block #95,389,917
12 transactions · 11 stateful · 2026-08-12 16:13:40 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,389,917
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrder
#3
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
batchUpdate
#8
setData
#9
0x59558d29
#10
execOrders
#11
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x151b88cc…996c
0x34b655…2a6f
2 touches
0 conflicts
0x172b2494…0d57
0x34b655…2a6f
2 touches
0 conflicts
0x226ae29a…2612
0x34b655…2a6f
2 touches
0 conflicts
0x24602217…9af8
0x34b655…2a6f
2 touches
0 conflicts
0x2840c278…bbc7
0x34b655…2a6f
2 touches
0 conflicts
0x3a7fb5b5…f0e5
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
0x442e26a30f…bbe968
Audit this contract →
← previous block
·
next block →
recent activity