pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,586,534
← previous block
next block →
recent activity
Analyzing
Block #92,586,534
9 transactions · 8 stateful · 2026-08-02 20:40:47 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,586,534
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
setData
#6
execOrders
· blocks 1
#7
execOrders
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd7607e…9b4b
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x1683a436…2c42
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0327b211…2766
0x34b655…2a6f
2 touches
0 conflicts
0x22cf1403…46f3
0x34b655…2a6f
2 touches
0 conflicts
0x2b0da3da…c9f3
0x34b655…2a6f
2 touches
0 conflicts
0x2ca3a7a0…e60d
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
0xddd7607e2b…ef9b4b
Audit this contract →
← previous block
·
next block →
recent activity