pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,732,971
← previous block
next block →
recent activity
Analyzing
Block #97,732,971
13 transactions · 12 stateful · 2026-08-20 21:40:03 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,732,971
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
updatePrices
#3
execOrders
#4
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#6
updatePosition
#7
0x3f5c179b
#8
0xaf47a8bb
#9
forward
#10
setData
#11
execOrders
#12
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
11
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xe41626f9…dd93
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x48d4896a…d0c6
0x34b655…2a6f
2 touches
0 conflicts
0x4b3e45f7…d2de
0x34b655…2a6f
2 touches
0 conflicts
0x5f251b96…6054
0x34b655…2a6f
2 touches
0 conflicts
0x65bdc5fa…d7f3
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity