pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,939,432
← previous block
next block →
recent activity
Analyzing
Block #98,939,432
9 transactions · 7 stateful · 2026-08-25 03:41:53 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,939,432
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x59558d29
#3
updateDataFeedsValuesPartial
#4
withdraw
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
setData
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41335ddf…94b9
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x26d8622c…e8af
0x34b655…2a6f
2 touches
0 conflicts
0x50c2d612…2f61
0x34b655…2a6f
2 touches
0 conflicts
0x65bdc5fa…d7f3
0x34b655…2a6f
2 touches
0 conflicts
0x92ead3f4…0d4b
0x34b655…2a6f
2 touches
0 conflicts
0xa92c8763…6d7f
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
0x41335ddf94…5594b9
Audit this contract →
← previous block
·
next block →
recent activity