pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,271,579
← previous block
next block →
recent activity
Analyzing
Block #99,271,579
16 transactions · 15 stateful · 2026-08-26 07:39:47 UTC
Parallelism
88
/100
Blocked
7
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,271,579
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updatePrices
#3
0xab083028
· blocks 1
#5
0x5acec890
#6
0x59558d29
#7
execPerpOps
#8
execPerpOps
#9
setData
#10
0x3f5c179b
#11
updatePosition
#12
execFwdPositionOpsV2
#13
forward
#14
forward
#15
execOrders
#4
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b1daf3c…cae1
0x34b655…2a6f
2 touches
0 conflicts
0x171d9a84…b3b7
0x34b655…2a6f
2 touches
0 conflicts
0x5d186724…a536
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x666ee004…0cb2
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity