pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,666,806
← previous block
next block →
recent activity
Analyzing
Block #96,666,806
11 transactions · 11 stateful · 2026-08-17 03:18:52 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,666,806
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
· blocks 2
#4
execOrders
#5
execOrders
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
0x3f5c179b
#9
0x3f5c179b
#10
setData
#2
execOrder
· blocks 1
#3
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x007bc07f…792f
0x34b655…2a6f
2 touches
0 conflicts
0x19e69334…a345
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x57b57f51…2449
0x34b655…2a6f
2 touches
0 conflicts
0x75586248…f0b4
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
3 conflicts on slot
0x53f393fafd…2a00b9
Audit this contract →
← previous block
·
next block →
recent activity