pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,396,874
← previous block
next block →
recent activity
Analyzing
Block #95,396,874
8 transactions · 8 stateful · 2026-08-12 16:48:50 UTC
Parallelism
38
/100
Blocked
50
%
Avg conflicts / tx
1.25
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,396,874
· 8 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
execOrder
· blocks 4
#3
0x3f5c179b
#7
setData
#2
execOrder
· blocks 3
#4
execFwdPositionOps
· blocks 2
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
5
w3
6
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
8 touches
6 conflicts
0xea674754…0e82
0x34b655…2a6f
8 touches
6 conflicts
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0x5b9528ae…c472
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0x1cdfe548…d3aa
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
10 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity