pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,732,464
← previous block
next block →
recent activity
Analyzing
Block #98,732,464
11 transactions · 10 stateful · 2026-08-24 10:20:19 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,732,464
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x59558d29
#4
execPerpOps
#5
batchUpdate
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
· blocks 1
#9
setData
#10
execOrders
#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
0x845ec8b0…c1af
0x34b655…2a6f
4 touches
1 conflict
0xc46d4148…aa5b
0x34b655…2a6f
4 touches
1 conflict
0x64ee3f3e…5f79
0x34b655…2a6f
4 touches
1 conflict
0x78860c4f…cade
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…004b
0x80c745…7210
2 touches
0 conflicts
0x00000000…004c
0x80c745…7210
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
0x845ec8b071…13c1af
Audit this contract →
← previous block
·
next block →
recent activity