pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,307,110
← previous block
next block →
recent activity
Analyzing
Block #101,307,110
11 transactions · 11 stateful · 2026-09-02 10:41:38 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,307,110
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updatePrices
#3
0xab083028
· blocks 1
#5
0x59558d29
#6
0xaf47a8bb
#7
execFwdPositionOpsV2
#8
verifyOracleProofV2
#9
forward
#10
0x6a97fdda
#4
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0b104f98…d9ee
0xc8689a…ee79
4 touches
1 conflict
0x40970e69…da50
0x34ae4d…3fc5
4 touches
1 conflict
0x901b2a81…7af9
0xa6afd3…d132
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x71b2cda1…822c
0x34ae4d…3fc5
2 touches
1 conflict
0xc625209a…cf22
0x34ae4d…3fc5
2 touches
1 conflict
0x607cd305…061b
0xa6afd3…d132
2 touches
1 conflict
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