pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,667,129
← previous block
next block →
recent activity
Analyzing
Block #101,667,129
12 transactions · 11 stateful · 2026-09-03 16:53:01 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
#101,667,129
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
execOrders
· blocks 1
#3
0x0c7abd22
· blocks 1
#4
0x5acec890
#5
setData
#6
updatePosition
#7
0x57368ddf
#9
execOrders
#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
2
w0
3
w0
8
w1
10
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdbb571e4…6829
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
0x34b655…2a6f
2 touches
0 conflicts
0x3c9eb1c3…9acf
0x34b655…2a6f
2 touches
0 conflicts
0x461661b9…f714
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity