pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,029,668
← previous block
next block →
recent activity
Analyzing
Block #100,029,668
11 transactions · 11 stateful · 2026-08-28 23:29:44 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,029,668
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xab083028
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x59558d29
#5
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
· blocks 1
#8
0x6a921a5f
#9
setData
#6
batchUpdate
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
7
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ad2f4bc…1800
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0ef48dcf…9c20
0x34b655…2a6f
2 touches
0 conflicts
0x19aa92ee…bfab
0x34b655…2a6f
2 touches
0 conflicts
0x19e94e5e…dcab
0x34b655…2a6f
2 touches
0 conflicts
0x3dc9f1ae…c0fc
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
0x2ad2f4bc01…9d1800
Audit this contract →
← previous block
·
next block →
recent activity