pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,594,998
← previous block
next block →
recent activity
Analyzing
Block #95,594,998
12 transactions · 11 stateful · 2026-08-13 09:26:09 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,594,998
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
0x5acec890
· blocks 1
#6
execFwdPositionOps
#7
setData
#8
0x59558d29
#9
execOrders
· blocks 1
#10
execOrders
#5
execFwdPositionOps
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
9
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x796c1a47…2bfb
0x34b655…2a6f
4 touches
1 conflict
0xb0b7842b…9379
0x34b655…2a6f
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
2 touches
0 conflicts
0x0b87c899…c0f9
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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
0x08636046fc…69e60f
Audit this contract →
← previous block
·
next block →
recent activity