pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#107,803,258
← previous block
next block →
recent activity
Analyzing
Block #107,803,258
23 transactions · 18 stateful · 2026-09-25 04:56:38 UTC
Parallelism
91
/100
Blocked
6
%
Avg conflicts / tx
0.04
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#107,803,258
· 23 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x59558d29
#3
execPerpOps
#4
execPerpOps
#5
execFwdPositionOpsV2
#7
executeBatch
#8
0xed82b078
#9
setData
#10
0xc7068c7b
#11
0x61d59c2d
#12
0x61d59c2d
#13
0x61d59c2d
#14
0x61d59c2d
#15
execOrders
#16
execOrders
#17
execOrders
#18
execOrders
#19
execOrders
#20
execOrders
#21
execOrders
#22
execOrders
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5ff2657f…c133
0xa6afd3…d132
4 touches
1 conflict
0xcd92ceb8…b9d2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002e
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity