pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,430,814
← previous block
next block →
recent activity
Analyzing
Block #106,430,814
12 transactions · 11 stateful · 2026-09-20 09:45:15 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,430,814
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x3d7f02…58e0
#2
updatePrices
#3
0x5acec890
· blocks 1
#4
0x59558d29
#5
execPerpOps
#6
executeBatch
#7
setData
#9
forward
#10
execFwdPositionOpsV2
#11
execOrders
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x856c6dbe…c790
0x34b655…2a6f
4 touches
1 conflict
0xc8f755b6…7b04
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x51fc8795…1266
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x6f2e3f2c…e745
0x34b655…2a6f
2 touches
0 conflicts
0x74b21dc5…d799
0x34b655…2a6f
2 touches
0 conflicts
0xa3d78e5e…bb33
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
0x856c6dbefd…30c790
Audit this contract →
← previous block
·
next block →
recent activity