pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,989,087
← previous block
next block →
recent activity
Analyzing
Block #94,989,087
11 transactions · 9 stateful · 2026-08-11 06:24:04 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,989,087
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
increaseLiquidity
#2
0x5acec890
#3
0x0f6795d9
#4
0x0f6795d9
#5
placeAndExecuteMarketSell
· blocks 1
#7
updateDataFeedsValuesPartial
#8
transfer
#9
setData
#10
0x59558d29
#6
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
2 touches
0 conflicts
0x6237f1a7…2f59
0x3bd359…433a
2 touches
0 conflicts
0xade01615…64aa
0x3bd359…433a
2 touches
0 conflicts
0xbfbf6aaf…2e9d
0x3bd359…433a
2 touches
0 conflicts
0xf6893bcb…3ff2
0x46a15b…4364
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:
USDC (USDC)
1 conflict on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity