pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,914,220
← previous block
next block →
recent activity
Analyzing
Block #98,914,220
14 transactions · 11 stateful · 2026-08-25 01:35:04 UTC
Parallelism
79
/100
Blocked
18
%
Avg conflicts / tx
0.14
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,914,220
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
execute
#4
execOrders
#5
0x59558d29
#6
execPerpOps
#7
execPerpOps
#8
execPerpOps
#9
execPerpOps
#10
execFwdPositionOpsV2
#12
execFwdPositionOpsV2
#13
setData
#2
0x0c7abd22
· blocks 1
#11
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xc650bc25…5ad5
0x851145…3f07
4 touches
1 conflict
0xae3ebcf3…3b04
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity