pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,063,103
← previous block
next block →
recent activity
Analyzing
Block #92,063,103
5 transactions · 4 stateful · 2026-08-01 00:48:17 UTC
Parallelism
60
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,063,103
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
setData
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8b8fbde…396d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
2 touches
0 conflicts
0x14420c60…fe43
0x34b655…2a6f
2 touches
0 conflicts
0x17637b08…707f
0x34b655…2a6f
2 touches
0 conflicts
0x176b9cd2…048a
0x34b655…2a6f
2 touches
0 conflicts
0x1f6f8ff8…a5d4
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
0xa8b8fbdeaa…29396d
Audit this contract →
← previous block
·
next block →
recent activity