pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,895,228
← previous block
next block →
recent activity
Analyzing
Block #101,895,228
10 transactions · 7 stateful · 2026-09-04 12:00:33 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,895,228
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x928e4afa
#2
0x0c7abd22
#3
0x0c7abd22
#4
0x0c7abd22
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#7
setData
#8
forward
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9935284…f313
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x14826371…f99d
0x34b655…2a6f
2 touches
0 conflicts
0x2a949bb2…8769
0x34b655…2a6f
2 touches
0 conflicts
0x2eb15031…f48d
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x57330c5d…9973
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
0xf99352848d…74f313
Audit this contract →
← previous block
·
next block →
recent activity