pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,526,602
← previous block
next block →
recent activity
Analyzing
Block #95,526,602
8 transactions · 6 stateful · 2026-08-13 03:42:08 UTC
Parallelism
63
/100
Blocked
67
%
Avg conflicts / tx
0.75
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,526,602
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 4
#6
updateDataFeedsValuesPartial
#7
0x0736e3…2b54
#2
0x5acec890
· blocks 1
#4
execFwdPositionOps
· blocks 1
#3
0x5acec890
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5a1b2fe…5369
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x128664cc…be3d
0x34b655…2a6f
2 touches
0 conflicts
0x159cff26…7665
0x34b655…2a6f
2 touches
0 conflicts
0x16778714…a6c9
0x34b655…2a6f
2 touches
0 conflicts
0x4b8db3ce…d59b
0x34b655…2a6f
2 touches
0 conflicts
0x500b09ac…dabd
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
3 conflicts on slot
0xc5a1b2febf…f05369
Audit this contract →
← previous block
·
next block →
recent activity