pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,869,098
← previous block
next block →
recent activity
Analyzing
Block #100,869,098
10 transactions · 10 stateful · 2026-08-31 21:57:45 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
#100,869,098
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
matchOrders
#4
0x5acec890
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
0x6a95f951
#3
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc635614b…2aa6
0xc8689a…ee79
4 touches
1 conflict
0x3ba7edbb…80e6
0x34ae4d…3fc5
4 touches
1 conflict
0x46279ae7…20dd
0x34ae4d…3fc5
4 touches
1 conflict
0x7f4a8466…f2cc
0x34ae4d…3fc5
4 touches
1 conflict
0xc0551ca5…e5d1
0x34ae4d…3fc5
4 touches
1 conflict
0xe49b1b9b…0be1
0x34ae4d…3fc5
4 touches
1 conflict
0xf1fbcd40…9515
0x34ae4d…3fc5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
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: Settlement / Helper
1 conflict on slot
0xc635614b20…b12aa6
Audit this contract →
← previous block
·
next block →
recent activity