pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,198,818
← previous block
next block →
recent activity
Analyzing
Block #97,198,818
13 transactions · 13 stateful · 2026-08-19 00:07:54 UTC
Parallelism
77
/100
Blocked
23
%
Avg conflicts / tx
0.31
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,198,818
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
transfer
#2
matchOrders
#3
0x6ad2e98b
#4
handleOps
· blocks 2
#5
placeAndExecuteMarketBuy
· blocks 1
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
transferWithAuthorization
#12
setData
#6
placeAndExecuteMarketSell
#7
handleOps
· blocks 1
#8
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0659a3f…90d9
0x000000…a032
6 touches
3 conflicts
0x00000000…000f
0x78999c…f371
6 touches
3 conflicts
0x34b1e500…7687
0x754704…b603
6 touches
3 conflicts
0x00000000…000b
0x78999c…f371
6 touches
3 conflicts
0x00000000…000b
0x754704…b603
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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:
0x00000000…7da032
3 conflicts on slot
0xe0659a3f75…9f90d9
Audit this contract →
← previous block
·
next block →
recent activity