pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,048,577
← previous block
next block →
recent activity
Analyzing
Block #100,048,577
10 transactions · 8 stateful · 2026-08-29 01:04:54 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,048,577
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
0xab083028
#4
execOrders
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
· blocks 2
#8
execFwdPositionOpsV2
· blocks 1
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x032ec3de…2902
0x34b655…2a6f
6 touches
3 conflicts
0x1867b653…e61b
0x34b655…2a6f
6 touches
3 conflicts
0xc74e9884…27a6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xea154cbb…f280
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x82a21578…a099
0x34b655…2a6f
5 touches
3 conflicts
0x2f02d4df…3567
0x34b655…2a6f
5 touches
3 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
3 conflicts on slot
0x032ec3de95…da2902
Audit this contract →
← previous block
·
next block →
recent activity