pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,716,411
← previous block
next block →
recent activity
Analyzing
Block #95,716,411
8 transactions · 8 stateful · 2026-08-13 19:37:52 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,716,411
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
0x5acec890
#3
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#7
setData
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x497517b8…6c90
0x34b655…2a6f
4 touches
1 conflict
0xb4527790…c282
0x34b655…2a6f
4 touches
1 conflict
0x26744466…9f4c
0x34b655…2a6f
2 touches
0 conflicts
0x3be75497…9a3c
0x34b655…2a6f
2 touches
0 conflicts
0x478e71ff…6cc6
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
0x08636046fc…69e60f
Audit this contract →
← previous block
·
next block →
recent activity