pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,202,357
← previous block
next block →
recent activity
Analyzing
Block #95,202,357
11 transactions · 9 stateful · 2026-08-12 00:17:39 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,202,357
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
#3
execOrder
· blocks 1
#4
0x5acec890
· blocks 1
#5
0xae92a63a
#6
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#7
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x57b02276…db3f
0x34b655…2a6f
4 touches
1 conflict
0xb514ce62…3397
0x34b655…2a6f
4 touches
1 conflict
0x460e76af…e1c3
0x34b655…2a6f
2 touches
0 conflicts
0x5c1e4658…3669
0x34b655…2a6f
2 touches
0 conflicts
0x5f752320…7f90
0x34b655…2a6f
2 touches
0 conflicts
0x681dd2e1…ce40
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity