pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,527,531
← previous block
next block →
recent activity
Analyzing
Block #95,527,531
10 transactions · 10 stateful · 2026-08-13 03:46:49 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,527,531
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x94defb17
· blocks 1
#7
execFwdPositionOps
· blocks 1
#9
setData
#6
0x94defb17
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801851bd…0baa
0x968279…9342
4 touches
1 conflict
0x6eee9cc8…03e0
0x968279…9342
4 touches
1 conflict
0x6eee9cc8…03e1
0x968279…9342
4 touches
1 conflict
0x6eee9cc8…03e4
0x968279…9342
4 touches
1 conflict
0x6eee9cc8…03e5
0x968279…9342
4 touches
1 conflict
0x6eee9cc8…03e6
0x968279…9342
4 touches
1 conflict
0x801851bd…0ba7
0x968279…9342
4 touches
1 conflict
0x801851bd…0ba8
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0x801851bdbd…730baa
Audit this contract →
← previous block
·
next block →
recent activity