pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,676,703
← previous block
next block →
recent activity
Analyzing
Block #98,676,703
9 transactions · 8 stateful · 2026-08-24 05:36:10 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
#98,676,703
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#4
0x59558d29
#6
execFwdPositionOpsV2
#7
0x3f5c179b
#8
setData
#2
0x5acec890
· blocks 2
#3
0x5acec890
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x074c08f8…fb56
0x34b655…2a6f
4 touches
1 conflict
0x4c20d376…0819
0x34b655…2a6f
4 touches
1 conflict
0x0505bae8…b4fb
0x34b655…2a6f
2 touches
0 conflicts
0x81ceb686…4df3
0x34b655…2a6f
2 touches
0 conflicts
0x09ac4956…a9df
0x34b655…2a6f
2 touches
0 conflicts
0x12e7c471…901c
0x34b655…2a6f
2 touches
0 conflicts
0x23df630a…22a5
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
1 conflict on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity