pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,573,635
← previous block
next block →
recent activity
Analyzing
Block #92,573,635
12 transactions · 9 stateful · 2026-08-02 19:35:53 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,573,635
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
executeBatch
#6
execOrders
#7
execOrders
#8
setData
#9
0x59558d29
· blocks 2
#10
0x59558d29
· blocks 1
#11
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01590810…1cec
0x34b655…2a6f
2 touches
0 conflicts
0x19dbe5ec…19cb
0x34b655…2a6f
2 touches
0 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
2 touches
0 conflicts
0x1f27097a…c619
0x34b655…2a6f
2 touches
0 conflicts
0x28c180e1…f1e2
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:
0x80c74517…647210
3 conflicts on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity