pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,565,372
← previous block
next block →
recent activity
Analyzing
Block #100,565,372
14 transactions · 11 stateful · 2026-08-30 20:29:29 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,565,372
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
updatePrices
#3
0x6ad2e98b
#4
0xc65a79…f415
#5
0x59558d29
#6
execPerpOps
#7
execOrders
#8
execPerpOps
#9
setData
#10
execFwdPositionOpsV2
· blocks 1
#12
execFwdPositionOpsV2
#13
getRoboTokens
#11
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x733c7779…a647
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x035a6eb3…6463
0x34b655…2a6f
2 touches
0 conflicts
0x0c8ff56c…7750
0x34b655…2a6f
2 touches
0 conflicts
0x6a8fc683…7cca
0x34b655…2a6f
2 touches
0 conflicts
0x78306506…38a5
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
0x733c7779fd…f4a647
Audit this contract →
← previous block
·
next block →
recent activity