pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,187,747
← previous block
next block →
recent activity
Analyzing
Block #99,187,747
12 transactions · 11 stateful · 2026-08-26 00:37:56 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,187,747
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
matchOrders
#3
0xab083028
· blocks 1
#4
0x5acec890
#5
0x59558d29
#6
executeBatch
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
0x6a8e35db
#11
setData
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65021fef…b735
0xa6afd3…d132
4 touches
1 conflict
0x71717491…10cf
0xa6afd3…d132
4 touches
1 conflict
0x92f41d1f…4258
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x10abefc9…c9bc
0x2b46c0…1669
2 touches
0 conflicts
0x1b9f9b78…a2b7
0x2b46c0…1669
2 touches
0 conflicts
0x2a981bf0…9528
0x2b46c0…1669
2 touches
0 conflicts
0x2f4b2cf9…4e1e
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
0x65021fefe6…cfb735
Audit this contract →
← previous block
·
next block →
recent activity