pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,229,212
← previous block
next block →
recent activity
Analyzing
Block #100,229,212
12 transactions · 11 stateful · 2026-08-29 16:14:24 UTC
Parallelism
75
/100
Blocked
27
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,229,212
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execute
#3
matchOrders
#4
execOrders
#5
0x59558d29
#6
execOrders
#7
execFwdPositionOpsV2
· blocks 1
#9
setData
#8
execFwdPositionOpsV2
#10
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w0
8
w1
10
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7f5b55…4994
0x34b655…2a6f
4 touches
1 conflict
0x00f19757…9252
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6c71e822…1263
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
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
0xfd7f5b557f…f74994
Audit this contract →
← previous block
·
next block →
recent activity