pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,290,109
← previous block
next block →
recent activity
Analyzing
Block #99,290,109
10 transactions · 10 stateful · 2026-08-26 09:13:00 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,290,109
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 1
#4
claimTax
#5
executeBatch
#6
0x94defb17
#8
setData
#9
0x61d59c2d
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x834e4143…18c0
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7a73b5ea…8857
0x34b655…2a6f
3 touches
1 conflict
0x706c758c…2fdb
0x34b655…2a6f
2 touches
0 conflicts
0x75f36d60…8556
0x34b655…2a6f
2 touches
0 conflicts
0xad601853…1d2a
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
0x834e41434e…9118c0
Audit this contract →
← previous block
·
next block →
recent activity