pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,194,758
← previous block
next block →
recent activity
Analyzing
Block #95,194,758
8 transactions · 6 stateful · 2026-08-11 23:39:26 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
#95,194,758
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
#2
updateDataFeedsValuesPartial
#3
placeAndExecuteMarketBuy
· blocks 2
#6
updateTemporalNumericValuesV1
#7
setData
#4
placeAndExecuteMarketBuy
· blocks 1
#5
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57abba4d…f159
0x40c49f…2af0
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x6b8ec392…dbf9
0x34b655…2a6f
2 touches
0 conflicts
0x7cddbfcb…0d29
0x34b655…2a6f
2 touches
0 conflicts
0x8c4c1c16…2c7d
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:
0x40c49f17…d22af0
3 conflicts on slot
0x57abba4d3f…c4f159
Audit this contract →
← previous block
·
next block →
recent activity