pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,981,465
← previous block
next block →
recent activity
Analyzing
Block #94,981,465
9 transactions · 7 stateful · 2026-08-11 05:45:44 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,981,465
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
#2
placeAndExecuteMarketBuy
· blocks 2
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a7ab780
#8
setData
#3
placeAndExecuteMarketBuy
· blocks 1
#4
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x9ed79474…9c1e
0x851145…3f07
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35e
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x5b113bff…d60d
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
3 conflicts on slot
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity