pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,038,594
← previous block
next block →
recent activity
Analyzing
Block #106,038,594
15 transactions · 15 stateful · 2026-09-19 00:51:18 UTC
Parallelism
87
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,038,594
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0x928e4afa
#3
updatePrices
#4
0xab083028
#5
execOrders
#6
0x3e2e8792
#7
0x59558d29
#8
execPerpOps
· blocks 1
#10
setData
#11
execFwdPositionOpsV2
#12
updatePosition
#13
forward
#14
execOrders
#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
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0dfebe1d…6083
0x09475a…400f
2 touches
0 conflicts
0x3d4d8630…d9e3
0x09475a…400f
2 touches
0 conflicts
0x57fa4d26…b852
0x09475a…400f
2 touches
0 conflicts
0x741048ab…1e62
0x09475a…400f
2 touches
0 conflicts
0xee2e48fa…c427
0x09475a…400f
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
0xe5bb3628b5…71e5e8
Audit this contract →
← previous block
·
next block →
recent activity