pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,781,452
← previous block
next block →
recent activity
Analyzing
Block #95,781,452
12 transactions · 10 stateful · 2026-08-14 01:05:00 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,781,452
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
execute
#4
execPerpOps
#5
execPerpOps
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
· blocks 1
#9
placeAndExecuteMarketBuy
#10
0x4ae78460
#11
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8c615d4…5da3
0x34b655…2a6f
4 touches
1 conflict
0x320a4123…4d39
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x164c2ed8…aa5f
0x34b655…2a6f
2 touches
0 conflicts
0x167b8502…d072
0x34b655…2a6f
2 touches
0 conflicts
0x1ab4c88c…49f2
0x34b655…2a6f
2 touches
0 conflicts
0x2029b74e…c206
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
0xc8c615d41e…025da3
Audit this contract →
← previous block
·
next block →
recent activity