pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,180,354
← previous block
next block →
recent activity
Analyzing
Block #95,180,354
6 transactions · 6 stateful · 2026-08-11 22:27:00 UTC
Parallelism
33
/100
Blocked
50
%
Avg conflicts / tx
0.83
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,180,354
· 6 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x5acec890
· blocks 2
#5
setData
#2
execFwdPositionOps
· blocks 2
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa226690…99ba
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0x0aa42ae9…ed69
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0x2bad40ae…0522
0x34b655…2a6f
4 touches
1 conflict
0x32891ad2…ba35
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
3 conflicts on slot
0xaa226690a1…5799ba
Audit this contract →
← previous block
·
next block →
recent activity