pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,244,816
← previous block
next block →
recent activity
Analyzing
Block #95,244,816
6 transactions · 6 stateful · 2026-08-12 03:52:07 UTC
Parallelism
50
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,244,816
· 6 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x41a8f47c
#2
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x96dd83e6…a507
0x34b655…2a6f
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0xd421a518…8b5c
0x5dd8f3…c69c
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
2 touches
0 conflicts
0x57f2a444…88a5
0x754704…b603
2 touches
0 conflicts
0x5f55f2c8…8f11
0x754704…b603
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:
Perpl
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity