pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,152,588
← previous block
next block →
recent activity
Analyzing
Block #95,152,588
10 transactions · 9 stateful · 2026-08-11 20:07:20 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,152,588
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x4d8dc985
#2
updateDataFeedsValuesPartial
#3
0xe2dc7dc3
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x94defb17
· blocks 2
#9
setData
#7
0x94defb17
· blocks 1
#8
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4ca9b11…4123
0x968279…9342
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x62cc972a…0824
0x968279…9342
6 touches
3 conflicts
0x62cc972a…0825
0x968279…9342
6 touches
3 conflicts
0x62cc972a…0828
0x968279…9342
6 touches
3 conflicts
0x62cc972a…0829
0x968279…9342
6 touches
3 conflicts
0x62cc972a…082a
0x968279…9342
6 touches
3 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:
0x96827978…f09342
3 conflicts on slot
0xf4ca9b1134…af4123
Audit this contract →
← previous block
·
next block →
recent activity