pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,672,958
← previous block
next block →
recent activity
Analyzing
Block #98,672,958
11 transactions · 10 stateful · 2026-08-24 05:16:40 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,672,958
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
· blocks 1
#3
0xab083028
#4
execOrders
#5
execOrders
#6
0x59558d29
#7
execPerpOps
#8
execFwdPositionOpsV2
#10
setData
#9
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa366dc41…b2d8
0xa6afd3…d132
4 touches
1 conflict
0x3f2100d8…f9b5
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd850f798…00e8
0xa6afd3…d132
3 touches
1 conflict
0x6634def9…6ded
0xa6afd3…d132
3 touches
1 conflict
0x5cbf0c7a…35ea
0xa6afd3…d132
3 touches
1 conflict
0xc8dc7682…a916
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0028
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0xa366dc411e…d4b2d8
Audit this contract →
← previous block
·
next block →
recent activity