pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,381,703
← previous block
next block →
recent activity
Analyzing
Block #95,381,703
11 transactions · 9 stateful · 2026-08-12 15:32:03 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
#95,381,703
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
execFwdPositionOps
· blocks 1
#7
0xed82b078
#8
0x6a7c926b
#9
setData
#10
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0x0bfc83e5…e8eb
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0xab29fc62…9506
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x690f644f…08ae
0x34b655…2a6f
2 touches
0 conflicts
0x951e757c…8eca
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
0x038b92433d…c5553d
Audit this contract →
← previous block
·
next block →
recent activity