pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,453,797
← previous block
next block →
recent activity
Analyzing
Block #99,453,797
12 transactions · 9 stateful · 2026-08-26 22:57:05 UTC
Parallelism
83
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,453,797
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x6ad2e98b
#3
0x5acec890
#4
0x59558d29
#5
execPerpOps
#6
execPerpOps
#7
execFwdPositionOpsV2
· blocks 3
#10
setData
#8
execFwdPositionOpsV2
#9
execOrders
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe6835a1…a184
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0df4
0x34b655…2a6f
4 touches
1 conflict
0xef7bc6de…2aaf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x3378650d…efcd
0x34b655…2a6f
4 touches
1 conflict
0x383a031b…b585
0x34b655…2a6f
4 touches
1 conflict
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
0xbe6835a18c…f1a184
Audit this contract →
← previous block
·
next block →
recent activity