pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,319,617
← previous block
next block →
recent activity
Analyzing
Block #99,319,617
9 transactions · 8 stateful · 2026-08-26 11:41:25 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,319,617
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
execOrders
· blocks 2
#4
0x3f5c179b
#7
execFwdPositionOpsV2
#8
approve
#5
execFwdPositionOpsV2
· blocks 1
#6
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76fbc5f5…2dc8
0x34b655…2a6f
6 touches
3 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
4 touches
1 conflict
0x03d74b49…2b86
0x34b655…2a6f
4 touches
1 conflict
0x1da3ce84…9bb8
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0x76fbc5f514…032dc8
Audit this contract →
← previous block
·
next block →
recent activity