pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,736,099
← previous block
next block →
recent activity
Analyzing
Block #98,736,099
8 transactions · 8 stateful · 2026-08-24 10:38:36 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,736,099
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
execFwdPositionOpsV2
· blocks 1
#3
execFwdPositionOpsV2
· blocks 1
#5
setData
#6
execOrders
· blocks 1
#4
execFwdPositionOpsV2
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b77
0x34b655…2a6f
4 touches
1 conflict
0x9b6c3273…9421
0x34b655…2a6f
4 touches
1 conflict
0xa771fb55…48d2
0x34b655…2a6f
4 touches
1 conflict
0xc44d9a29…10e2
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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
0x6d1b72eefe…416b77
Audit this contract →
← previous block
·
next block →
recent activity