pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,021,573
← previous block
next block →
recent activity
Analyzing
Block #95,021,573
9 transactions · 7 stateful · 2026-08-11 09:07:30 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,021,573
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
placeAndExecuteMarketSell
· blocks 1
#6
placeAndExecuteMarketSell
#8
setData
#7
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0xaacaeaa2…a14a
0x40c49f…2af0
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x145e321c…aee3
0x34b655…2a6f
2 touches
0 conflicts
0x24ca1902…7a87
0x34b655…2a6f
2 touches
0 conflicts
0x98a1bad6…5130
0x34b655…2a6f
2 touches
0 conflicts
0xa3a621f8…75a2
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x3a921be0eb…41779c
Audit this contract →
← previous block
·
next block →
recent activity