pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,442,497
← previous block
next block →
recent activity
Analyzing
Block #92,442,497
14 transactions · 13 stateful · 2026-08-02 08:36:19 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,442,497
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#4
0xed82b078
#5
0x6a6f01fb
#6
setData
#7
execOrders
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#13
0x59558d29
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59a07ac0…728d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04994ed2…9032
0x34b655…2a6f
2 touches
0 conflicts
0x0b710c61…e052
0x34b655…2a6f
2 touches
0 conflicts
0x19fb7d60…da48
0x34b655…2a6f
2 touches
0 conflicts
0x27754bd4…96ae
0x34b655…2a6f
2 touches
0 conflicts
0x2d6fda24…c638
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
0x59a07ac0ce…5c728d
Audit this contract →
← previous block
·
next block →
recent activity