pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,698,000
← previous block
next block →
recent activity
Analyzing
Block #94,698,000
12 transactions · 10 stateful · 2026-08-10 05:58:28 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
#94,698,000
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execPerpOps
#3
execPerpOps
#4
0x5acec890
#5
execFwdPositionOps
#6
0x3f5c179b
#7
0x6a7968fc
#8
setData
#9
0xcc99f3…2421
#10
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x165ceb94…e9c3
0x34b655…2a6f
2 touches
0 conflicts
0x2e1f5171…ad2d
0x34b655…2a6f
2 touches
0 conflicts
0x7c93b38a…9e69
0x34b655…2a6f
2 touches
0 conflicts
0x9210e826…1414
0x34b655…2a6f
2 touches
0 conflicts
0xa91b05f7…a560
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
0x217bd767aa…4fb79e
Audit this contract →
← previous block
·
next block →
recent activity