pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,751,502
← previous block
next block →
recent activity
Analyzing
Block #93,751,502
9 transactions · 7 stateful · 2026-08-06 22:21:55 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,751,502
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
placeAndExecuteMarketBuy
· blocks 1
#7
0x6a75097b
#8
setData
#5
placeAndExecuteMarketBuy
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xe6b87cc1…aa89
0x40c49f…2af0
4 touches
1 conflict
0x595233b5…c4aa
0x754704…b603
4 touches
1 conflict
0x91eb94de…b47b
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x33b392cc…4b28
0xd18b7e…414b
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity