pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,152,853
← previous block
next block →
recent activity
Analyzing
Block #100,152,853
11 transactions · 10 stateful · 2026-08-29 09:50:02 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,152,853
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
0x5acec890
· blocks 2
#5
execPerpOps
#6
execPerpOps
#7
execFwdPositionOpsV2
#9
setData
#10
bet
#4
0x928e4afa
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x191e0467…70e5
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x006551fe…c052
0x34b655…2a6f
2 touches
0 conflicts
0x143561e1…aa9a
0x34b655…2a6f
2 touches
0 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x1b740895…f754
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity