pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,951,087
← previous block
next block →
recent activity
Analyzing
Block #94,951,087
10 transactions · 9 stateful · 2026-08-11 03:12:58 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,951,087
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
#3
updatePrices
#4
0x5acec890
#5
placeAndExecuteMarketSell
· blocks 2
#8
updateDataFeedsValuesPartial
#9
setData
#6
placeAndExecuteMarketSell
· blocks 1
#7
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0x2c0c1605…df99
0x851145…3f07
6 touches
3 conflicts
0x4c1fbdf6…953d
0x754704…b603
4 touches
1 conflict
0x1adf396f…c667
0x01bff4…1071
4 touches
1 conflict
0x3352fed8…8092
0x01bff4…1071
4 touches
1 conflict
0x915c095e…c1e5
0x2b46c0…1669
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
3 conflicts on slot
0x07b86c515d…73cdae
Audit this contract →
← previous block
·
next block →
recent activity