pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,397,171
← previous block
next block →
recent activity
Analyzing
Block #97,397,171
12 transactions · 10 stateful · 2026-08-19 17:15:49 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,397,171
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
0x6cfade05
#5
execFwdPositionOpsV2
#6
forward
#7
forward
#8
setData
#9
0x4cb2db39
· blocks 1
#10
0x59558d29
#11
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w0
10
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x000bde1a…e123
0x34b655…2a6f
2 touches
0 conflicts
0x1b7497b2…0af8
0x34b655…2a6f
2 touches
0 conflicts
0x221a6ee3…2a3c
0x34b655…2a6f
2 touches
0 conflicts
0x3048129a…ca10
0x34b655…2a6f
2 touches
0 conflicts
0x39875c49…67dc
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…00004c
Audit this contract →
← previous block
·
next block →
recent activity