pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,538,999
← previous block
next block →
recent activity
Analyzing
Block #93,538,999
11 transactions · 8 stateful · 2026-08-06 04:33:37 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,538,999
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
#3
0x0f6795d9
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
placeAndExecuteMarketBuy
#7
0x94defb17
· blocks 1
#9
setData
#10
execOrders
#8
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0344fc81…41ce
0x34b655…2a6f
2 touches
0 conflicts
0x0344fc81…41cf
0x34b655…2a6f
2 touches
0 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x19e3f7bb…37fd
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
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
0x177211e248…161c2d
Audit this contract →
← previous block
·
next block →
recent activity