pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,298,609
← previous block
next block →
recent activity
Analyzing
Block #95,298,609
7 transactions · 7 stateful · 2026-08-12 08:31:04 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,298,609
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
· blocks 1
#4
bet
#5
forward
#6
setData
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0x000bde1a…e123
0x34b655…2a6f
4 touches
1 conflict
0x24e76b5e…25c7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5c806a17…a094
0x34b655…2a6f
4 touches
1 conflict
0x660d9107…f97f
0x34b655…2a6f
4 touches
1 conflict
0x660d9107…f980
0x34b655…2a6f
4 touches
1 conflict
0x6e689c48…a06b
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
0xe5eb3c3335…0c0e3a
Audit this contract →
← previous block
·
next block →
recent activity