pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,225,952
← previous block
next block →
recent activity
Analyzing
Block #100,225,952
14 transactions · 11 stateful · 2026-08-29 15:58:00 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,225,952
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a9301ff
#2
updatePrices
#3
updatePrices
#4
execOrders
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x5acec890
#8
0x59558d29
#9
setData
#10
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
#12
0xed82b078
#13
0x6a9301ff
#7
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00af2567…c002
0x34b655…2a6f
2 touches
0 conflicts
0x1368c0ff…46af
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x38befc08…20c8
0x34b655…2a6f
2 touches
0 conflicts
0x5086c64a…28ba
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
0x1b5d2e607a…9999b5
Audit this contract →
← previous block
·
next block →
recent activity