pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,570,986
← previous block
next block →
recent activity
Analyzing
Block #93,570,986
10 transactions · 8 stateful · 2026-08-06 07:14:25 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,570,986
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
handleOps
#2
swapAndStartBridgeTokensViaNEARIntents
#3
verifyOracleProofV2
#4
0x29eed2d3
#5
execFwdPositionOps
· blocks 2
#8
updateDataFeedsValuesPartial
#9
setData
#6
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x185bfe72…cd37
0x34b655…2a6f
4 touches
1 conflict
0x5e71af98…bfd6
0x34b655…2a6f
4 touches
1 conflict
0x14eb4b87…f393
0x000000…a032
2 touches
0 conflicts
0x20c030a1…c348
0x000000…a032
2 touches
0 conflicts
0x23cdb8ed…1396
0x000000…a032
2 touches
0 conflicts
0x2a3d16ea…8576
0x000000…a032
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
3 conflicts on slot
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity