pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,241,618
← previous block
next block →
recent activity
Analyzing
Block #99,241,618
11 transactions · 10 stateful · 2026-08-26 05:08:59 UTC
Parallelism
82
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,241,618
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updatePrices
· blocks 1
#4
updatePrices
#5
0xab083028
· blocks 2
#7
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
execOrders
#3
updatePrices
#6
fulfillWithERC20
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f2100d8…f9b5
0xa6afd3…d132
4 touches
1 conflict
0x7ea1cfdf…81c0
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
2 touches
0 conflicts
0x10d80fee…dbda
0x2b46c0…1669
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
0x3f2100d80a…98f9b5
Audit this contract →
← previous block
·
next block →
recent activity