pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#109,131,440
← previous block
next block →
recent activity
Analyzing
Block #109,131,440
12 transactions · 9 stateful · 2026-09-29 20:28:34 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#109,131,440
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x61d59c2d
#2
0x5acec890
· blocks 1
#3
0xab083028
#4
0x5acec890
#5
execPerpOps
#6
updatePrices
#7
execFwdPositionOpsV2
#8
0xed82b078
#9
0xed82b078
#10
setData
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x742e5c25…a6b2
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05006bd2…56ad
0x508254…98bd
2 touches
0 conflicts
0x05006bd2…56b7
0x508254…98bd
2 touches
0 conflicts
0x05006bd2…56da
0x508254…98bd
2 touches
0 conflicts
0x05006bd2…56e3
0x508254…98bd
2 touches
0 conflicts
0x05006bd2…56ea
0x508254…98bd
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
0x742e5c25e5…73a6b2
Audit this contract →
← previous block
·
next block →
recent activity