pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,561,248
← previous block
next block →
recent activity
Analyzing
Block #98,561,248
12 transactions · 11 stateful · 2026-08-23 19:34:43 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,561,248
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xa96df62f
#3
execOrders
#4
0x86fa9c…98a3
#5
0x59558d29
#6
execPerpOps
#7
execFwdPositionOpsV2
· blocks 1
#9
execOrders
#10
0x6a8b4bcb
#11
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xa94c3b09…26c7
0x34b655…2a6f
4 touches
1 conflict
0xa94c3b09…26c8
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xd1a9e7f0…12df
0x34b655…2a6f
4 touches
1 conflict
0xeeb442b1…ba1d
0x34b655…2a6f
4 touches
1 conflict
0xde510023…5a9a
0x34b655…2a6f
3 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity