pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,275,798
← previous block
next block →
recent activity
Analyzing
Block #99,275,798
9 transactions · 8 stateful · 2026-08-26 08:01:00 UTC
Parallelism
67
/100
Blocked
38
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,275,798
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6c0954…3d0a
#2
0x5acec890
· blocks 1
#3
0x59558d29
#7
forward
#8
setData
#4
execFwdPositionOpsV2
· blocks 2
#5
execFwdPositionOpsV2
#6
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d8078fe…ed70
0x34b655…2a6f
4 touches
1 conflict
0x40d6d1e9…131e
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xd6cc7093…3ead
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
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
0x9d8078fe74…bced70
Audit this contract →
← previous block
·
next block →
recent activity