pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,427,344
← previous block
next block →
recent activity
Analyzing
Block #95,427,344
11 transactions · 10 stateful · 2026-08-12 19:22:53 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,427,344
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
· blocks 1
#8
0x222d4ad6
#9
setData
#10
0x59558d29
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x649d7bd5…77cf
0x34b655…2a6f
4 touches
1 conflict
0x83da2486…8024
0x34b655…2a6f
4 touches
1 conflict
0x6e54dbdd…3231
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0x427d1120…4eb1
0x34b655…2a6f
2 touches
0 conflicts
0x4ce893aa…fe4d
0x34b655…2a6f
2 touches
0 conflicts
0x766a9366…8da1
0x34b655…2a6f
2 touches
0 conflicts
0x8faba3a7…8454
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
0x649d7bd56c…3977cf
Audit this contract →
← previous block
·
next block →
recent activity