pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,561,407
← previous block
next block →
recent activity
Analyzing
Block #93,561,407
12 transactions · 11 stateful · 2026-08-06 06:26:16 UTC
Parallelism
83
/100
Blocked
27
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,561,407
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
· blocks 1
#2
matchOrders
#3
updatePrices
#4
execOrders
#5
0x5acec890
· blocks 2
#6
execFwdPositionOps
#7
0x3f5c179b
#10
setData
#8
placeAndExecuteMarketBuy
#9
execOrders
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
8
w1
9
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x200ed648…912f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x0610892c…fee0
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x7aa512ae…d2e0
0x754704…b603
2 touches
0 conflicts
0x7f03e539…f4cc
0x754704…b603
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:
Coinbase Wrapped BTC (cbBTC)
1 conflict on slot
0x2b54cadb82…7c4425
Audit this contract →
← previous block
·
next block →
recent activity