pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,143,801
← previous block
next block →
recent activity
Analyzing
Block #96,143,801
9 transactions · 7 stateful · 2026-08-15 07:28:05 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,143,801
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execPerpOps
#3
execPerpOps
#4
execOrders
· blocks 1
#5
execFwdPositionOpsV2
· blocks 1
#7
setData
#6
execFwdPositionOpsV2
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a49f3bf…713b
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x5e71af98…bfd6
0x34b655…2a6f
4 touches
1 conflict
0x7f20e79f…1a25
0x34b655…2a6f
4 touches
1 conflict
0x998a1167…81f9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
0x2a49f3bf2a…9b713b
Audit this contract →
← previous block
·
next block →
recent activity