pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,872,353
← previous block
next block →
recent activity
Analyzing
Block #100,872,353
10 transactions · 8 stateful · 2026-08-31 22:14:08 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,872,353
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
setData
#4
setData
#5
execFwdPositionOpsV2
· blocks 1
#6
0x3f5c179b
#8
execFwdPositionOpsV2
#9
transfer
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x09aa4c28…6ab1
0x34b655…2a6f
2 touches
0 conflicts
0x22badbc6…4c24
0x34b655…2a6f
2 touches
0 conflicts
0x3155f770…4f6d
0x34b655…2a6f
2 touches
0 conflicts
0x39bef825…5bee
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
0xe1c4e5ce15…770dec
Audit this contract →
← previous block
·
next block →
recent activity