pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,130,163
← previous block
next block →
recent activity
Analyzing
Block #96,130,163
10 transactions · 8 stateful · 2026-08-15 06:19:27 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,130,163
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute302
· blocks 2
#4
commitVerification
#5
0xab083028
#6
0x5acec890
#7
0x000000b2
#8
execFwdPositionOpsV2
#9
setData
#2
execute302
· blocks 1
#3
execute302
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c63247…ce02
0x0a3323…0a3c
6 touches
3 conflicts
0x446f2734…8b54
0x0a3323…0a3c
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x1a31be72…cd74
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x4c214bb3…c5d3
0x34b655…2a6f
2 touches
0 conflicts
0x67bfbc55…7b2f
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:
0x0a332311…6e0a3c
3 conflicts on slot
0x52c63247e1…bace02
Audit this contract →
← previous block
·
next block →
recent activity