pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,554,668
← previous block
next block →
recent activity
Analyzing
Block #95,554,668
10 transactions · 8 stateful · 2026-08-13 06:03:18 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,554,668
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0x5acec890
· blocks 2
#4
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
bet
#8
setData
#9
0x59558d29
#3
0x5acec890
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaae6463e…bfcc
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x8d8f609d…ea99
0x34b655…2a6f
4 touches
1 conflict
0x203f132b…89fc
0x34b655…2a6f
2 touches
0 conflicts
0x2631ed70…fb7f
0x34b655…2a6f
2 touches
0 conflicts
0x3a984784…dd19
0x34b655…2a6f
2 touches
0 conflicts
0x3c9835fe…6fde
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
0xaae6463e2e…b6bfcc
Audit this contract →
← previous block
·
next block →
recent activity