pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,161,920
← previous block
next block →
recent activity
Analyzing
Block #95,161,920
14 transactions · 12 stateful · 2026-08-11 20:54:17 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,161,920
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
executeBatch
#7
batchUpdate
#8
0x94defb17
· blocks 1
#10
0x0f6795d9
#11
0x0f6795d9
#12
setData
#13
0x39435dac
#9
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33fa06d0…6314
0x968279…9342
4 touches
1 conflict
0x33fa06d0…6315
0x968279…9342
4 touches
1 conflict
0x33fa06d0…6318
0x968279…9342
4 touches
1 conflict
0x33fa06d0…6319
0x968279…9342
4 touches
1 conflict
0x33fa06d0…631a
0x968279…9342
4 touches
1 conflict
0x5b7b46b1…9866
0x968279…9342
4 touches
1 conflict
0x5b7b46b1…9867
0x968279…9342
4 touches
1 conflict
0x5b7b46b1…9869
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
0x33fa06d0c6…bd6314
Audit this contract →
← previous block
·
next block →
recent activity