pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,008,157
← previous block
next block →
recent activity
Analyzing
Block #95,008,157
13 transactions · 10 stateful · 2026-08-11 08:00:00 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.31
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,008,157
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
execOrders
· blocks 1
#3
0x6ad2e98b
· blocks 1
#4
execOrder
· blocks 1
#5
execOrder
· blocks 1
#6
execOrders
#7
updateDataFeedsValuesPartial
#10
batchUpdate
#11
setMerkleRoot
#12
setData
#8
placeAndExecuteMarketBuy
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w0
5
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bf90b57…998a
0x851145…3f07
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x21280422…0930
0x34b655…2a6f
4 touches
1 conflict
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x94de4d05…ad01
0x34b655…2a6f
4 touches
1 conflict
0xa28c0ab9…f737
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 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:
0x851145ea…9f3f07
1 conflict on slot
0x6bf90b57ba…68998a
Audit this contract →
← previous block
·
next block →
recent activity