pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,195,838
← previous block
next block →
recent activity
Analyzing
Block #99,195,838
10 transactions · 10 stateful · 2026-08-26 01:18:39 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,195,838
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 2
#4
0x3f5c179b
#7
forward
#8
0x6a8e3f66
#9
setData
#5
execFwdPositionOpsV2
· blocks 1
#6
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2202504e…fad0
0x34b655…2a6f
6 touches
3 conflicts
0x9f2f322b…2a81
0x34b655…2a6f
6 touches
3 conflicts
0x9a8482cc…8bee
0x34b655…2a6f
6 touches
3 conflicts
0x6f75f880…8c39
0x34b655…2a6f
4 touches
1 conflict
0xe4555b5c…8150
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0x5fc46fa5…096a
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
0x2202504ef1…9ffad0
Audit this contract →
← previous block
·
next block →
recent activity