pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,041,091
← previous block
next block →
recent activity
Analyzing
Block #102,041,091
15 transactions · 13 stateful · 2026-09-05 00:20:04 UTC
Parallelism
80
/100
Blocked
15
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,041,091
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
0x59558d29
#4
execPerpOps
#5
execPerpOps
#6
setData
#7
handleOps
· blocks 2
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#12
0x6a9b6037
#13
execOrders
#14
execOrders
#10
handleOps
· blocks 1
#11
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
10
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0659a3f…90d9
0x000000…a032
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4b0d99f4…2969
0x000000…a032
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x1c796c6b…064e
0x34b655…2a6f
2 touches
0 conflicts
0x6ca15e14…7be8
0x34b655…2a6f
2 touches
0 conflicts
0x15425236…b698
0x350035…7777
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:
0x00000000…7da032
3 conflicts on slot
0xe0659a3f75…9f90d9
Audit this contract →
← previous block
·
next block →
recent activity