pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,756,009
← previous block
next block →
recent activity
Analyzing
Block #98,756,009
13 transactions · 13 stateful · 2026-08-24 12:18:52 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,756,009
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
#3
execOrder
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x59558d29
#6
execFwdPositionOpsV2
· blocks 1
#7
0x94defb17
#8
forward
#9
forward
#11
setData
#12
execOrders
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9c83a7b1…e305
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe029f67b…d048
0x34b655…2a6f
4 touches
1 conflict
0x1b7f7926…4ad2
0x34b655…2a6f
2 touches
0 conflicts
0x23529e13…6f25
0x34b655…2a6f
2 touches
0 conflicts
0x25180879…8191
0x34b655…2a6f
2 touches
0 conflicts
0x2827ae77…4368
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity