pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,000,736
← previous block
next block →
recent activity
Analyzing
Block #95,000,736
13 transactions · 11 stateful · 2026-08-11 07:22:40 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,000,736
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0x5acec890
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
placeAndExecuteMarketSell
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x3eaa26…e76b
#11
execOrders
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a89094e…f5b2
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3246eb65…c06e
0x065c9d…c394
2 touches
0 conflicts
0x6e390f98…c914
0x065c9d…c394
2 touches
0 conflicts
0xb32cd1a3…5bfe
0x065c9d…c394
2 touches
0 conflicts
0xf577e616…8bf7
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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:
Perpl
1 conflict on slot
0x9a89094e2b…f6f5b2
Audit this contract →
← previous block
·
next block →
recent activity