pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,714,365
← previous block
next block →
recent activity
Analyzing
Block #95,714,365
11 transactions · 9 stateful · 2026-08-13 19:27:32 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,714,365
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x5acec890
· blocks 1
#3
0xcffefd2e
· blocks 1
#5
0xcffefd2e
#6
updateDataFeedsValuesPartial
#7
0x915df74d
#8
forward
#9
transferWithAuthorization
#10
setData
#4
0xcffefd2e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef1de905…0582
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x628359b1…7263
0x34b655…2a6f
4 touches
1 conflict
0x280bd9bd…f01d
0x34b655…2a6f
2 touches
0 conflicts
0x5d1ac445…5233
0x34b655…2a6f
2 touches
0 conflicts
0x6f4e7625…aba5
0x34b655…2a6f
2 touches
0 conflicts
0x6f8644f7…10fa
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
0xef1de9056f…9e0582
Audit this contract →
← previous block
·
next block →
recent activity