pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,552,356
← previous block
next block →
recent activity
Analyzing
Block #95,552,356
7 transactions · 7 stateful · 2026-08-13 05:51:41 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,552,356
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#3
repayWithCollateral
#4
execFwdPositionOps
#5
setData
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd93edb3f…94ec
0x34b655…2a6f
4 touches
1 conflict
0x45d3434f…6c0c
0x34b655…2a6f
4 touches
1 conflict
0xe9452241…95a3
0x34b655…2a6f
4 touches
1 conflict
0x1637d9f2…a9e5
0x34b655…2a6f
2 touches
0 conflicts
0x22b1a321…6823
0x34b655…2a6f
2 touches
0 conflicts
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x3b2235f9…c676
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
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:
Perpl
1 conflict on slot
0xd93edb3f20…0394ec
Audit this contract →
← previous block
·
next block →
recent activity