pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,971,293
← previous block
next block →
recent activity
Analyzing
Block #94,971,293
8 transactions · 6 stateful · 2026-08-11 04:54:35 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,971,293
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x320c0058
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
placeAndExecuteMarketBuy
· blocks 2
#7
setData
#5
placeAndExecuteMarketBuy
· blocks 1
#6
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xc06b9f02…80e3
0x851145…3f07
6 touches
3 conflicts
0x12c7832e…1ba4
0x34b655…2a6f
2 touches
0 conflicts
0x20efa2f1…85f1
0x34b655…2a6f
2 touches
0 conflicts
0x2145086e…39c6
0x34b655…2a6f
2 touches
0 conflicts
0x2b5101ac…090b
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