pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,858,642
← previous block
next block →
recent activity
Analyzing
Block #105,858,642
10 transactions · 10 stateful · 2026-09-18 09:44:33 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,858,642
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
#3
0x5acec890
#4
0x3e2e8792
· blocks 1
#5
0x59558d29
#6
claimRewards
#7
0x3f5c179b
#9
0x61d59c2d
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29cd05f5…390c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1e0d4dd0…1755
0x34b655…2a6f
2 touches
0 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
2 touches
0 conflicts
0x3c9b10c1…d791
0x34b655…2a6f
2 touches
0 conflicts
0x4118bd12…924a
0x34b655…2a6f
2 touches
0 conflicts
0x464bb4b6…12a1
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
0x29cd05f5e7…a9390c
Audit this contract →
← previous block
·
next block →
recent activity