pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,205,662
← previous block
next block →
recent activity
Analyzing
Block #99,205,662
9 transactions · 9 stateful · 2026-08-26 02:08:04 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,205,662
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
#3
0x59558d29
#4
allocate
#5
batchUpdate
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x20e46e7f…1e46
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x5f761bb5…b2f6
0x34b655…2a6f
4 touches
1 conflict
0x79fbc843…d076
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
0xe1c4e5ce15…770dec
Audit this contract →
← previous block
·
next block →
recent activity