pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,985,098
← previous block
next block →
recent activity
Analyzing
Block #95,985,098
12 transactions · 8 stateful · 2026-08-14 18:09:39 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,985,098
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xa96df62f
#3
execOrders
#4
0x5acec890
#5
execFwdPositionOpsV2
· blocks 1
#7
0xb19b44…293d
#8
0x8f1a71…8c24
#9
0x1f56f1…52db
#10
0xcb150e…20aa
#11
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35a9f06c…7689
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0547420b…fc46
0x34b655…2a6f
2 touches
0 conflicts
0x06d96035…9aec
0x34b655…2a6f
2 touches
0 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
2 touches
0 conflicts
0x30c5329c…711c
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
0x35a9f06ccf…e37689
Audit this contract →
← previous block
·
next block →
recent activity