pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,249,096
← previous block
next block →
recent activity
Analyzing
Block #100,249,096
12 transactions · 11 stateful · 2026-08-29 17:55:12 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
#100,249,096
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x6ad2e98b
#3
execPerpOps
#4
execPerpOps
#5
execPerpOps
#6
executeBatch
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7212
0x34b655…2a6f
2 touches
0 conflicts
0xea02471d…1539
0x34b655…2a6f
2 touches
0 conflicts
0x8649e48f…941c
0xc8689a…ee79
2 touches
0 conflicts
0x09e0690d…6e3d
0xe52b14…7230
2 touches
0 conflicts
0x0a107ca3…d51d
0xe52b14…7230
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
0x74e485b13a…f0d380
Audit this contract →
← previous block
·
next block →
recent activity