pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,114,460
← previous block
next block →
recent activity
Analyzing
Block #95,114,460
11 transactions · 8 stateful · 2026-08-11 16:55:33 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,114,460
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
execOrder
#3
execPerpOps
#4
0x5acec890
#6
execFwdPositionOps
#7
0x3f5c179b
#8
updateDataFeedsValuesPartial
#9
0x6a7b547d
#10
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
4 touches
1 conflict
0x6aab0ebf…30b7
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05527801…9c11
0x34b655…2a6f
2 touches
0 conflicts
0x064bb149…79fd
0x34b655…2a6f
2 touches
0 conflicts
0x2385516f…eca5
0x34b655…2a6f
2 touches
0 conflicts
0x319a48e0…7b26
0x34b655…2a6f
2 touches
0 conflicts
0x32a38ad9…ef17
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
0xa56e54d018…f82d39
Audit this contract →
← previous block
·
next block →
recent activity