pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,442,651
← previous block
next block →
recent activity
Analyzing
Block #102,442,651
14 transactions · 13 stateful · 2026-09-06 10:14:59 UTC
Parallelism
86
/100
Blocked
15
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,442,651
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
0xa96df62f
#4
0xab083028
#5
execOrders
#6
0x5acec890
#7
0x5acec890
#8
0x5acec890
#9
execOrder
· blocks 1
#10
0x59558d29
#11
setData
#13
execOrders
#2
swap
#12
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4aefb5c6…bf40
0x81a224…7777
2 touches
1 conflict
0x49baa92f…35f0
0x188d58…ea8e
2 touches
0 conflicts
0x49baa92f…35f2
0x188d58…ea8e
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity