pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,696,872
← previous block
next block →
recent activity
Analyzing
Block #92,696,872
11 transactions · 10 stateful · 2026-08-03 05:56:39 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,696,872
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a702e0e
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1efc452b…3550
0x34b655…2a6f
4 touches
1 conflict
0x91d1a0a3…8cba
0x34b655…2a6f
4 touches
1 conflict
0xf009b1a8…d02d
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x1efc452b…354f
0x34b655…2a6f
4 touches
1 conflict
0x2672f1ec…9fd7
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
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
0x1efc452b2b…753550
Audit this contract →
← previous block
·
next block →
recent activity