pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,427,378
← previous block
next block →
recent activity
Analyzing
Block #95,427,378
11 transactions · 10 stateful · 2026-08-12 19:23:03 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,427,378
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
execOrders
#4
0x5acec890
· blocks 1
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x59558d29
#5
0x5acec890
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf607560e…828a
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xec45e3d8…65c1
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
2 touches
0 conflicts
0x91b8c157…148e
0x34b655…2a6f
2 touches
0 conflicts
0x959e17ee…0830
0x34b655…2a6f
2 touches
0 conflicts
0x98e2e7cd…e4c2
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
0xf607560e69…3f828a
Audit this contract →
← previous block
·
next block →
recent activity