pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,775,985
← previous block
next block →
recent activity
Analyzing
Block #98,775,985
11 transactions · 10 stateful · 2026-08-24 13:59:24 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,775,985
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
0x59558d29
#5
batchUpdate
#6
execFwdPositionOpsV2
· blocks 1
#8
setData
#9
0x34653439
#10
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe389496e…6be8
0x34b655…2a6f
4 touches
1 conflict
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0xd7049f78…c1e1
0x34b655…2a6f
4 touches
1 conflict
0x202f71e7…3369
0x34b655…2a6f
2 touches
0 conflicts
0x2be34971…27ba
0x34b655…2a6f
2 touches
0 conflicts
0x49b0842d…0a93
0x34b655…2a6f
2 touches
0 conflicts
0x55559831…164f
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
0xe389496e04…966be8
Audit this contract →
← previous block
·
next block →
recent activity