pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,718,637
← previous block
next block →
recent activity
Analyzing
Block #95,718,637
11 transactions · 9 stateful · 2026-08-13 19:49:06 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,718,637
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x9cf9a051
· blocks 1
#4
execPerpOps
#5
execPerpOps
#6
0x5acec890
#7
updateDataFeedsValuesPartial
#8
0xf5d05576
#9
execFwdPositionOpsV2
#10
setData
#3
0x9cf9a051
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
0x00000000…0003
0x0a4fcb…a602
4 touches
1 conflict
0x00000000…0002
0x08dd3d…a583
4 touches
1 conflict
0x2b936aa5…05e2
0x141b1d…9583
4 touches
1 conflict
0x2b936aa5…05e3
0x141b1d…9583
4 touches
1 conflict
0x2b936aa5…05e5
0x141b1d…9583
4 touches
1 conflict
0x8591796e…6114
0x754704…b603
4 touches
1 conflict
0x92422ced…8761
0x754704…b603
4 touches
1 conflict
0xab39f3a1…b682
0x754704…b603
4 touches
1 conflict
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:
0x0a4fcba9…7ba602
1 conflict on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity