pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,994,069
← previous block
next block →
recent activity
Analyzing
Block #99,994,069
12 transactions · 12 stateful · 2026-08-28 20:30:31 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,994,069
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x6a91f05f
#5
0x59558d29
#6
batchUpdate
#7
execFwdPositionOpsV2
· blocks 1
#8
claim
#10
setData
#11
execOrders
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb367dbbf…adda
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xdb71568c…1dc5
0x34b655…2a6f
4 touches
1 conflict
0xf609bbef…e1c5
0x34b655…2a6f
4 touches
1 conflict
0x5ed1f9d0…fc7f
0x34b655…2a6f
4 touches
1 conflict
0xb367dbbf…add9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
0x1b6862…e19c
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
0xb367dbbf1a…4badda
Audit this contract →
← previous block
·
next block →
recent activity