pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#117,740,601
← previous block
next block →
recent activity
Analyzing
Block #117,740,601
13 transactions · 12 stateful · 2026-10-29 23:14:41 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#117,740,601
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x59558d29
#3
execOrders
#4
0x35e534ea
#5
0x35e534ea
#6
0x35e534ea
#7
0x5acec890
#8
execPerpOps
· blocks 1
#10
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
#12
setData
#9
execPerpOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x125f12…a50b
2 touches
0 conflicts
0x094dc0b1…69f3
0x34b655…2a6f
2 touches
0 conflicts
0x1d2aa1bc…95f7
0x34b655…2a6f
2 touches
0 conflicts
0x468c69db…851e
0x34b655…2a6f
2 touches
0 conflicts
0x6f94a6b5…5790
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
0x51fc8795c8…571266
Audit this contract →
← previous block
·
next block →
recent activity