pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,672,704
← previous block
next block →
recent activity
Analyzing
Block #97,672,704
14 transactions · 11 stateful · 2026-08-20 16:33:49 UTC
Parallelism
86
/100
Blocked
18
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,672,704
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0c7abd22
#3
execOrders
#4
execPerpOps
#5
execPerpOps
#6
0x0c7abd22
#7
0x0c7abd22
#8
batchUpdate
#9
execFwdPositionOpsV2
#10
setData
· blocks 1
#12
0x59558d29
· blocks 1
#11
setData
#13
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x1eb0fab5…3517
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity