pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,689,023
← previous block
next block →
recent activity
Analyzing
Block #92,689,023
13 transactions · 13 stateful · 2026-08-03 05:17:08 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,689,023
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
reallocate
#2
0xab083028
#3
updatePrices
#4
0x5acec890
· blocks 1
#5
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
0x3f5c179b
#9
execFwdPositionOps
#10
0x6a7024cb
#11
setData
#12
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1151b256…b43b
0x09475a…400f
2 touches
0 conflicts
0x3d4d8630…d9e3
0x09475a…400f
2 touches
0 conflicts
0x741048ab…1e62
0x09475a…400f
2 touches
0 conflicts
0xee2e48fa…c427
0x09475a…400f
2 touches
0 conflicts
0xb25823d5…e4d9
0x754704…b603
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity