pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,096,345
← previous block
next block →
recent activity
Analyzing
Block #100,096,345
10 transactions · 9 stateful · 2026-08-29 05:05:23 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,096,345
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x928e4afa
#2
0x59558d29
#3
execPerpOps
#4
execPerpOps
#5
executeBatch
#6
setData
#7
execFwdPositionOpsV2
· blocks 1
#8
0x3f5c179b
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85de3b93…8005
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x232d787f…7862
0x34b655…2a6f
3 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
2 touches
0 conflicts
0xea02471d…1539
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…004b
0x80c745…7210
2 touches
0 conflicts
0x00000000…004c
0x80c745…7210
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
0x85de3b93f0…b98005
Audit this contract →
← previous block
·
next block →
recent activity