pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,557,124
← previous block
next block →
recent activity
Analyzing
Block #95,557,124
11 transactions · 7 stateful · 2026-08-13 06:15:39 UTC
Parallelism
82
/100
Blocked
29
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,557,124
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0x088078…dace
#3
updateDataFeedsValuesPartial
#4
0x5acec890
· blocks 1
#6
execFwdPositionOps
· blocks 1
#8
0xed82b078
#9
setData
#10
0x59558d29
#5
0x5acec890
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf57ccd8…75b1
0x34b655…2a6f
4 touches
1 conflict
0xe533b16d…eeee
0x34b655…2a6f
4 touches
1 conflict
0xe8bff3cf…5740
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x3e950538…2259
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xcf57ccd8b3…3675b1
Audit this contract →
← previous block
·
next block →
recent activity